Talk:Silly Emplosions

I like these ideas:

1. If you leave a variable for too long without assigning a value, the variable will lose its value.
2. You can return from a function more than once to return multiple values from the function at the same time.
3. Sometimes it skips commands and doesn't do it right the first time so you have to repeat it sometimes.
4. If you try to read a value of a variable that isn't set yet, it will continue until a value is assigned, then it will go back and try again what it was trying to do before.
5. A return statement will not always know where to return to.

The others are kinda silly. --(this comment by Trinithis at 18:22, 30 December 2007 UTC; please sign your comments with ~~~~)

Well, I think that array indices starting at 0.5 is amusing, but many of the others are silly, IMHO. --Okohokonu 22:02, 16 March 2009 (UTC)

After all, it is called Silly Emplosions BradensEsolangs (talk) 18:40, 8 February 2019 (UTC)

At least one of the ideas in the list is implemented by CLC-INTERCAL; it's possible to set up a statement so that it runs the next time the variables mentioned in it exist. It also allows the source code to alter the compiler used to compile it, forcing a dynamic recompilation; this is not quite the same as one of the items mentioned, but has a similar effect. See also Java2K for commands not doing the right thing (although I don't like the way it was implemented in that language), and the non-esoteric language TECO for control codes in source code. --ais523 18:59, 2 January 2008 (UTC)

CONTRADICTIONS

'must be saved as .EXE'

'must be saved as .rt and written in Wingdings'

It is a list of ideas. They are not supposed to be all used in the same language. 93.106.77.85 06:11, 8 December 2015 (UTC)

Are you sure? However, it is not a contradiction to use the RTF format with EXE extension. --Zzo38 (talk) 07:37, 12 December 2015 (UTC)