1. IDE & Euphoria 3.0
IMHO an IDE (integrated development environment) is different from a
simple text editor, even one that lets you launch your program. here are
a few *key* differences...
1) an IDE allows you to *step through* statements one at a time
2) an IDE allows you to *watch variables* as the program runs
3) an IDE *manages projects* as a logical group of files
We should all thank David Cuny for providing us with the best possible
text editor to write Euphoria programs in. DONATE THOSE SMILEY DOLLARS!
I know that Euphoria includes the Trace ability, but this is extremely
limited.
Finally, I would like to throw my two cents in for the features of
Euphoria 3.0.
1) Data structures
2) A built-in (read: written in assembly) save/load of sequences or
structures. Random access if at all possible, linear access (like a text
file) would do though.
Here is the syntax I see for #1...
structure ClientRecord
sequence name
sequence address
sequence phone_number
atom age
atom salary
end sequence
ClientRecord bob
bob.name = "Bob Jones"
bob.address = "1221 West Toad Street"
bob.age = 30
This ties perfectly in with Euphoria's atom/sequence methodology. As it
stands now I have to write ".e" files with tons of "global constant"
statements for all the indexes into my data structures. For example,
this is how I would code the above...
global constant ClientRecord_Name = 1
global constant ClientRecord_Address = 2
global constant ClientRecord_Phone = 3
global constant ClientRecord_Age = 4
global constant ClientRecord_Salary = 5
sequence bob
bob = repeat ( 0 , 5 )
bob [ ClientRecord_Name ] = "Bob Jones"
bob [ ClientRecord_Age ] = 30
John DeHope.
2. Re: IDE & Euphoria 3.0
>IMHO an IDE (integrated development environment) is different from
>a simple text editor, here are a few *key* differences...
>1) an IDE allows you to *step through* statements one at a time
>2) an IDE allows you to *watch variables* as the program runs
>3) an IDE *manages projects* as a logical group of files
number 1 & 2 are handled in trace; you could probably write an editor
that manages .ex, .e, .pro, .exw, .ew files...
>We should all thank David Cuny for providing us with the best
>possible text editor to write Euphoria programs in. DONATE THOSE
>SMILEY DOLLARS!
which one is that? ;) $$$ :D $$$ :D $$$ :D
>I know that Euphoria includes the Trace ability, but this is
>extremely limited.
IMHO, I don't think trace is limited at all. Depending on where you place
'with trace' statements in your source files, you can just watch the
execution in your main .ex module, or watch everything in all of your
modules. You can watch variables too, which is extremely helpful for
debugging.
>1) Data structures
>Here is the syntax I see for #1...
>
> structure ClientRecord
> sequence name
> sequence address
> sequence phone_number
> atom age
> atom salary
> end sequence
>
> ClientRecord bob
>
> bob.name = "Bob Jones"
> bob.address = "1221 West Toad Street"
> bob.age = 30
I think structures are a good idea. Although it can be emulated using
nested sequences, I would prefer accessing elements by name and not by
index.
>2) A built-in (read: written in assembly) save/load of sequences
>or structures. Random access if at all possible, linear access
>(like a text file) would do though.
you can use get() to read native Euphoria sequences ( {1,'a',etc}}) from
a file. As for the text files, I would like to see that included; it's a
pain rewriting the same code over again all the time (that's why theres
cut&paste, right?).
----->Buddy
budmeister1 at juno.com
_____________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]
3. Re: IDE & Euphoria 3.0
John DeHope wrote:
> <snip>
> We should all thank David Cuny for providing us with the best possible
> text editor to write Euphoria programs in. DONATE THOSE SMILEY DOLLARS!
>
> I know that Euphoria includes the Trace ability, but this is extremely
> limited.
I disagree - I have used (and cursed) trace / debug "facilities" in
several
commercial languages, and aside from the awkward way of displaying
strings, the
Euphoria trace is the most usable of all.
I agree wholeheartedly with the following, however:
> Finally, I would like to throw my two cents in for the features of
> Euphoria 3.0.
> 1) Data structures
> 2) A built-in (read: written in assembly) save/load of sequences or
> structures. Random access if at all possible, linear access (like a text
> file) would do though.
>
> Here is the syntax I see for #1...
>
> structure ClientRecord
> sequence name
> sequence address
> sequence phone_number
> atom age
> atom salary
> end sequence -- (Don't you mean "end structure"?)
>
> ClientRecord bob
>
> bob.name = "Bob Jones"
> bob.address = "1221 West Toad Street"
> bob.age = 30
>
> This ties perfectly in with Euphoria's atom/sequence methodology. As it
> stands now I have to write ".e" files with tons of "global constant"
> statements for all the indexes into my data structures. For example,
> this is how I would code the above...
>
> global constant ClientRecord_Name = 1
> global constant ClientRecord_Address = 2
> global constant ClientRecord_Phone = 3
> global constant ClientRecord_Age = 4
> global constant ClientRecord_Salary = 5
>
> sequence bob
> bob = repeat ( 0 , 5 )
> bob [ ClientRecord_Name ] = "Bob Jones"
> bob [ ClientRecord_Age ] = 30
>
Not only that, but with the present situation, you lose the "safety" of
Euphoria's automatic type checking. Your suggested structure would
restore
type checking, preventing assignments like age = "twwnty" or salary =
"Fred".
A much needed improvement, plus it fits into the current way of doing
these
things as implemented in several other languages. Also, it's clear and
understandable.
Regards,
Irv
