1. wish lists etc - Reply
David,
I do not want to start a flame war over this, I can see your point.
But my point really is, that a large part of Euphoria's beauty is,
apart from lists, sorry sequences, in its simplicity. Anybody with a
background in one of the more common imperative languages (Basic, C,
Pascal, Fortran, etc) can start using it within half an hour, or
whatever it takes to scan the first part of the manual. And the CASE
statement you are advocating, has a pretty limited application,
depending, of course, on one's programing style. It is ok if the case
expression results in an integer. In other words, it is fine, if e.g.
you want to do something on Day 1, something else on Day 2 and 5, but
you are completely stuffed, if you want to program on Sunday only if
the weather is foul! Using the if clause, you simply tag the condition
on. But I might be wrong, again...
I like your pre-processor, that's ok, because it is an optional extra
and, more importantly, completely transparent. But I would not use it,
too much of a hassle, unless of course you can give us my favourite
conditional statement with the test at bottom of the loop, sort of
'repeat .. until'. But Robert has already stolen the 'repeat' part for
something else, so perhaps 'loop until'? Jiri.
And while I am at it, thanks to Jacques for his compliment (I wish I
could do things like his soundblaster routines!), and also many thanks
to Robert for the high resolution timer (tick_rate()). Jiri.
2. Re: wish lists etc - Reply
------------E36603B6BB51
I caught that part about lists!
I'd second the notion on simplicity. I've programmed in Visual
Basic, Pascal(aka Delphi), Java, C(++), and now I'm messin' with
euphoria. What is most attractive about euphoria is the simplicicty(I
hope I'm not lisping...)
On the other hand, I sure wouldn't mind a Rad tool for user
interface development(I'm lazy!).
------------E36603B6BB51
<HTML><BODY>
<DT>I caught that part about lists!</DT>
<DT> I'd second the notion on simplicity. I've programmed
in Visual Basic, Pascal(aka Delphi), Java, C(++), and now I'm messin' with
euphoria. What is most attractive about euphoria is the simplicicty(I hope
I'm not lisping...) </DT>
<DT> On the other hand, I sure wouldn't mind a Rad tool
for user interface development(I'm lazy!). </DT>
</HTML>
------------E36603B6BB51--
3. Re: wish lists etc - Reply
- Posted by Bob Paddock <bpaddock at EXECPC.COM>
Jan 05, 1997
-
Last edited Jan 06, 1997
>apart from lists, sorry sequences, in its simplicity. Anybody with a
>background in one of the more common imperative languages (Basic, C,
>Pascal, Fortran, etc) can start using it within half an hour, or
>whatever it takes to scan the first part of the manual. And the CASE
>statement you are advocating, has a pretty limited application,
Some thing that you can do with "C" CASE but not elsif if
have one case fall in to the next one via leaving out the
"Break".
>I like your pre-processor, that's ok, because it is an optional extra
>and, more importantly, completely transparent. But I would not use it,
>too much of a hassle....
That is what "MAKE" is for to hide these kind of hassles.
--
For information on any of the following check out my WEB site at:
http://www.execpc.com/~bpaddock/ or http://www.usachoice.net/bpaddock
Chemical Free Air Conditioning/No CFC's, Chronic Pain Relief, Electromedicine,
Electronics, Explore!, Free Energy, Full Disclosure, KeelyNet, Matric Limited,
Neurophone, Oil City PA, Philadelphia Experiment.
4. wish lists etc - Reply
*** Reply to note of 01/04/97 19:03
nor do i wish to start a flame war. i agree that simplicity in a language
is an important feature.
you are correct in stating that the 'CASE' is a weaker and more limited
version of the 'IF' statement. anything you would want to do with a 'CASE',
you can do with an 'IF' - and more. it's just one of those syntactic sugar
things.
i'm hardly dead set on a "CASE" statement; nor am i compelled to turn
Euphoria into a version of "C". for some time, the use of references
such as foo[i][3][j] had been gnawing at me. for me, they are one of the
'goto' of Euphoria code - quick and dirty, but hard to read in a month.
when i ran across the 'FOR x IN y' statement in ABC, it seemed ideal for
Euphoria: it mapped well into the language, and it added clarity to the
code. i wrote the pre-processor so people (myself included) could try it
themselves, and see if the idea has merit.
i think robert craig wouldn't mind me quoting him here:
"Once I've added a new language feature, I can never take it out.
I have to be very cautious."
amen to that.
re: adding an 'until' statement. i'll consider it, but there is one
problem. the nice thing about the 'WITH' statement is there is a 1:1
mapping between lines of input code and lines of output code. with
a 'REPEAT', you need to turn it into something like:
-- BEFORE -- AFTER
repeat while 1=1 do
... ...
until <condition> if <condition> then
exit
end if
end while
which is not a 1:1 mapping. this means that i would need a cross-reference
in order to map errors back to the source code. it's not all that difficult;
i just need to decide how far i want to take the program.
i'm preparing the next release of the pre-processor that aims to remove
the "hassle" in using it. it's coded, but i want to do a more thorough
job testing it before releasing it.
-- david cuny
