On Fri, 4 Nov 2005 01:26:13 -0600, "Pawel Slusarz"
<usenet@romaneseuntdomus.com> wrote, quoted or indirectly quoted
someone who said :

I presume you are doing some sort of unmaintainable code trick

int condition = 1;
 //...
 if (1==condition) {

 }
 if !(1==condition) {
 
 }

but that is not compilable java.

It is not clear which "sounds" you are trying to avoid. Or is it meant
as a general how-to for excluding any arbitrary sound?

If so, I would consider organizing the document into one chapter per
keyword, as keywords is the main thing you need to worry about. I
would guess that the most annoying words would be "public", "class",
"static", "void", "main" and "String". Others, like "import" are
trivially avoided.

Another topic of some interest might be how to handle the symbols of
the standard API (just in case you want the program to also do
something useful).

A more painless way to achieve this might be to start using a
preprocessor and just #define away your unwanted sounds, but that's a
bit like cheating :-)

Cheers
    Bent D

A few here appear to have missed the point - it's a game, or something to  
do to exercise your creativity a bit. See if you can write programs  
without using one or more standard constructs. In literature, it's often  
about writing text (sometimes whole books) without using the letter 'e',  
and just think what that precludes from your java code (else, new, return,  
etc).

(Aside: Try doing a 'find' for 'e' in the entire article text, source and  
all)

I assume the letter you try to avoid is "e", but you don't say so
anywhere. That makes the choices look somewhat arbitrary.

/L

   Very amusing.

   I tried figuring out how to do I/O, but came up with nothing. Dead ends
included:

   * use static imports to get the static operations of System without
actually mentioning System. Unfortunately, the static import itself mentions
System.
   * Throwing some sort of exception whose name doesn't contain 'e', while
setting its message to the desired output. Unfortunately, you have to
instantiate an exception before you can throw it.
   * Instantiating an Exception (or anything else) use Class.forName().
Unfortunately, this method throws an exception, which you must catch (and
thus mention), and the exception, and all of its parents, has 'e' in its
name.
   * Declaring and using annotations for something. I'm don't have much
experience with annotations, so I have no idea what kind of tricks could be
done with these.

   Of course, you could "cheat" and use \u0065 whereever you wanted to use
'e' but that would probably defeat the spirit of the challenge.

   - Oliver