1. Re: EUPHORIA Digest - 21 Jun 1998 to 22 Jun 1998 (#1998-36)
>Date: Wed, 24 Jun 1998 08:41:17 -0400
>From: Robert B Pilkington <bpilkington at JUNO.COM>
>Subject: Re: EUPHORIA Digest - 21 Jun 1998 to 22 Jun 1998 (#1998-36)
>
>I'm all for it! ;) (Actually, you'd also need to include the functions
>jedi_knight(), simcity(), mario(), wingcommander() and asteroids()... :)
sure, just make lotsa these 
procedure asteroids()
system("ex asteroid", 2)
end procedure
>What's undef? What's the $ needed in front of the variable? What type is
>x? Where is it defined? What is x if the file doesn't exist?
>With Euphoria, you don't have those questions
and have 300 statement limit instead, eh am I repeating that? 
>This might be more appropriate:
Haven't tried either, but I'm sure both should work...
>Plus, there are only three limitations with not registering:
>300 statement limit. Encrypting your code. Voting for the Micro-Economy.
Nice summary
>Yes, we all want our programs to mess around with the date and time on
>our computers... File attributes are more important, but how many times
>is that needed?
Lots, most of my pgms gets attr, clears it, opens the file, gets file
date/time, reads the file, process in memory, seek to beginning,
write modified version, sets file date/time back, closes the file,
restores attr. It'll infect your programs even if they are read-only ;->
>Actually, why even bother? WHY would you even worry about such a thing?
>Besides, Euphoria has a similar feature:
>
>Euphoria allows you to have Euphoria code in the program, and execute it,
>and tell you if it worked (it doesn't say anything), or if it has an
>error (it crashes and tells you.) No extra code, no unneccary double
>quotes, no "eval" statement.
Explain.
The eval statement allows you to read Perl statements from user
input or from a file or ... and execute them... how is that done
in Euphoria?
I can imagine a debugger (much better than Euph's current one)
being written in Euph to debug Euph programs, using eval ...
maybe a getstatement() would be handy as well, etc.
>Actually, Euphoria DOES have ?, but not ?:. :)
>
>? variable_name
>
>But the ?: is VERY, VERY hard to read, at least to me. I just can't
>understand the theory behind it. I don't really care, either... if..then
>you can tell what is happening just by looking at it. That is what
>Euphoria is all about.
Some languages (e.g. Visual Basic) balance the need of ?: and the
clarity, so
cond ? iftrue : iffalse
becomes
iif(cond, iftrue, iffalse)
(iif = immediate if)
at the cost of non-short-circuiting (all operands are evaluated).
Of course I can implement iif in Euphoria, except I can't handle
short-circuiting (only cond and one other operand are evaluated). 
