Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "javax.swing.JSnarker" Newsgroups: comp.lang.java.programmer Subject: Re: "Small" Program Challenge. Date: Sat, 23 Jun 2012 17:14:21 -0400 Organization: media lab? Lines: 30 Message-ID: References: <7kIDr.12088$Bp1.3039@newsfe10.iad> <4291u795eegvb0j8b09lvqkng3hh13t336@4ax.com> <4732eeb4-9d34-4765-ba6d-c098f0528038@googlegroups.com> <2P2dnb8yuIyntXzSnZ2dnUVZ8hGdnZ2d@giganews.com> NNTP-Posting-Host: z6+OOGUYUsKBuxh2BViJkQ.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: NewsTap/3.5.5 (iPhone/iPod Touch) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:15550 On 23/06/2012 5:10 PM, Wanja Gayk wrote: > In article , gharriman@boojum.mit.edu > says... >> >> On 23/06/2012 7:42 AM, Wanja Gayk wrote: >>> In article , gharriman@boojum.mit.edu >>> says... >>> >>>> Which would contravene the spec, since the spec clearly says that >>>> initialization must *precede* invocation. >>> >>> Between loading and initialization theres still verification, isn't it? >> >> Verification is a part of loading, rather than coming after it. > > I'm curious: How do you want to verify something that you haven't loaded > yet? I don't. Neither do I want a loaded class hanging around unverified afterward, though. So the two belong back-to-back. Essentially, obtaining the byte code from wherever into main memory is step 1 of loading, and verifying it is step 2. -- public final class JSnarker extends JComponent A JSnarker is an NNTP-aware component that asynchronously provides snarky output when the Ego.needsPuncturing() event is fired in cljp.