Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!goblin3!goblin.stu.neva.ru!exi-transit.telstra.net!news.telstra.net!exi-spool.telstra.net!exi-reader.telstra.net!not-for-mail Date: Fri, 27 May 2011 18:09:06 +1000 From: Esmond Pitt Reply-To: not.esmond.pitt@not.bigpond.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 Newsgroups: comp.lang.java.programmer Subject: Re: Java generics and type erasure References: <9d4c2b16-beb5-40b1-87a2-f03e971efeed@k17g2000vbn.googlegroups.com> <4dde10b0$0$67777$c30e37c6@exi-reader.telstra.net> <4ddf0617$0$67777$c30e37c6@exi-reader.telstra.net> <3f7c1f48-f025-48af-b6bd-20463f6651db@e13g2000vbo.googlegroups.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Lines: 9 Message-ID: <4ddf5c23$0$67779$c30e37c6@exi-reader.telstra.net> NNTP-Posting-Host: 120.151.14.51 X-Trace: 1306483747 exi-reader.telstra.net 67779 120.151.14.51:36510 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4643 On 27/05/2011 3:30 PM, Lew wrote: > erasure (the way I look at it) is a runtime phenomenon. I don't care if > it happened during compilation or class load. That doesn't make sense. Erasure is a state that has already been attained prior to execution. It can't be a runtime phenomenon as there hasn't been any runtime yet: indeed there may never be a runtime for it to be a phenomenon of, e.g. if the class is immediately recompiled prior to any execution, or indeed never executed at all.