Yes, that's a checked exception; thus, it must be caught. Unchecked exceptions will compile but then be thrown at runtime. Take care, Sina -----Original Message----- From: brailleblaster-bounce@xxxxxxxxxxxxx [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of qubit Sent: Saturday, December 11, 2010 2:09 PM To: brailleblaster@xxxxxxxxxxxxx Subject: [brailleblaster] Re: jspawn: stuck on a stupid nit Hi, thanks -- I have gotten past that one and am on to a bunch of editos -- and I do mean editos -- like typos only more elaborate... As soon as it compiles and I get the cat command to work with it, I will send to list. I certainly hope this has been more than just a learning experience for me -- I mean, I hope brailleblaster ends up using it. Interesting, javac won't compile something that throws exceptions unless you put it in a try block. I was going to do that later, but the compiler barfed at me. --le ----- Original Message ----- From: "Chris von See" <chris@xxxxxxxxxxxxx> To: <brailleblaster@xxxxxxxxxxxxx> Sent: Saturday, December 11, 2010 12:13 PM Subject: [brailleblaster] Re: jspawn: stuck on a stupid nit Try: import java.util.List; This statement should go right after your "package" directive, or right at the beginning of your file if you don't have a "package" directive. Then you can do things like this: List<String> stringList = new ArrayList<String>(); (assuming you also import java.util.ArrayList). Cheers Chris On Dec 11, 2010, at 10:07 AM, qubit wrote: > I am prevented from compiling my code by a simple matter of finding a > stupid example of what to import to get the list template. > Yes I searched the docs. I found List was in the Collections > framework under java.util. > So I have tried practically every import directive I can think of to > import it and they all fail. > > Can someone please fire off a one-liner telling me what to import or > declare or whatever so I can use a simple List<String>??? > I'm sure this isn't the last time I will use this class. > > I was planning on sending this this morning but this bug has been > wasting me too much time. > Thanks. > --le > >