Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!.POSTED!not-for-mail From: BGB Newsgroups: comp.lang.java.programmer Subject: Re: Managed-Code Bloat Date: Wed, 08 Jun 2011 03:54:43 -0700 Organization: albasani.net Lines: 44 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.albasani.net vtIVRRtZUxybwV87VO/upYru56jCeb1vUCj+LDF282vJ9SgUszjxCfgQoA+WwvgqZA7cnZCT8+neXXy+dOMpxw== NNTP-Posting-Date: Wed, 8 Jun 2011 10:58:02 +0000 (UTC) Injection-Info: news.albasani.net; logging-data="CcN1tRf6dXNbfuJ8i8hT3wiJ7zzU7Axab/3dvwV/OXcczUDy2hvnCXFpnEi0H2WvBdYzKYDukskXGtRtdLXi2Dyza7wo1KROszLyDSnsP4iittiCnTkgBgVWHze2Bj+g"; mail-complaints-to="abuse@albasani.net" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 In-Reply-To: Cancel-Lock: sha1:9NSl4y0d6EmF93VWQC8SyFGGFPw= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5087 On 6/8/2011 12:23 AM, Michal Kleczek wrote: > BGB wrote: > >> >> also, possible though are some garbage reduction tricks: >> ref-counting (as they can detect earlier objects that have died); >> (heap-based) value types (because their lifespan behavior is trivial to >> determine, and so one can allocate/free them aggressively); >> ... >> >> ref-counting has the drawback though that it is very difficult to write >> "general purpose" code and not screw up the ref-counts somewhere (which >> can easily blow up the program), causing me to generally not use them. >> > > There has been some work done to implement ref-counting GC in (Sun) JVM. > See: > http://www.cs.technion.ac.il/~erez/Papers/refcount.ps > The results were promissing but it has not been incorporated into production > JVM. > yeah... this is along with several other major features. one of my own prior VMs used ref-counting, but this, combined with other factors, made the VM in question very painful to work on (or interface with). my current VMs are much easier to work with, at a cost of being somewhat less efficient. another partial point of controversy in my current architecture, is that the core type-system is based mostly on strings and "strcmp()". again it was another tradeoff: strings were generally the least-effort option, and eventually largely won out in their battle against tagged references (which were technically "better", but also generally more of a pain to work with, vs using raw pointers and "magic" types). or such...