Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!goblin1!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:07:09 +1000
From: Esmond Pitt <esmond.pitt@bigpond.com>
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> <nospam-871A48.22542123052011@news.aioe.org> <irfgkl$lca$1@news.albasani.net> <Xns9EEF8515AF3B6vaj4088ianshef@138.125.254.103> <irh6kb$gse$1@news.albasani.net> <Xns9EEFA3AE378DDvaj4088ianshef@138.125.254.103> <irhhik$9rc$3@dont-email.me> <irjv7c$iv0$5@lust.ihug.co.nz> <irk9dr$j5p$4@dont-email.me> <irkc5t$q84$1@lust.ihug.co.nz> <irkkb6$c29$1@dont-email.me> <irkt4q$41b$2@lust.ihug.co.nz> <4dde10b0$0$67777$c30e37c6@exi-reader.telstra.net> <irlega$3kp$1@news.albasani.net> <4ddf0617$0$67777$c30e37c6@exi-reader.telstra.net> <irn1e0$gtb$1@news.albasani.net> <4ddf14c8$0$67785$c30e37c6@exi-reader.telstra.net> <irncmt$k84$1@news.albasani.net>
In-Reply-To: <irncmt$k84$1@news.albasani.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 8
Message-ID: <4ddf5baf$0$67779$c30e37c6@exi-reader.telstra.net>
NNTP-Posting-Host: 120.151.14.51
X-Trace: 1306483631 exi-reader.telstra.net 67779 120.151.14.51:36510
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4642

On 27/05/2011 3:27 PM, Lew wrote:
> The meaning of the assertion you cite was that the generics information
> that is present in the bytecode is ignored at runtime

No. There is no generic information in the bytecode to ignore. It has 
been erased by the compiler. The only generic information in the .class 
file is in the method signatures, and they are there for the compiler, 
not for the JVM.