Re: Euphoria vs. Visual Basic - the speed
>From: =A9koda
>Why should I use Euphoria and not Visual Basic?
When I use VB, I really feel boxed in. It seems, IMHO, that VB forces yo=
u
to do things in a certain way, and gives very little leeway. Eu has a lo=
t
more flexibility, in virtually any aspect. Granted, VB has many more
features built in, although win32lib has closed that gap a lot.
>Cause I think I'm gonna switch to Visual Basic if I don't get a good rea=
son
why not to.
>How is graphics and game development supported with Visual Basic?
I'd say it depends on what you mean by 'game.' Something like a
strategy/board type of game would probably work fairly well in VB, but I
wouldn't want to try much more than that, since VB's strenghts are really
for making app's that interface with databases (ie, business apps), not m=
ore
'freestyle' projects.
>What bothers me about euphoria:
=20
>It doesn't have a good IDE with good debugging. It has trace, but it's v=
ery
poor. For example, .>you can see only sequences that are small, if I have
string "C:\Euphoria\DEMO\DOS32\STEREO.EX" I >can only see
"C:\Euphoria\D...", there's no way I can see the whole string.You should
also be able >to view nested sequences in a treeview.
As mentioned earlier, there are a lot of ideas about improved tracing out
there. I doubt that you'll get a treeview, but at the top of my list is =
to
be able to look at arbitrary subscripts within trace mode.
>It doesn't support structures.
>It's not flexible enough (default argumens, atom a=3D2,...)
As David Cuny alluded, I think you're using the wrong word here, unless y=
ou
mean that you want multiple syntaxes for various tasks. Assign on
declaration might be nice, but I'm not sure it's really a reason to switc=
h
to VB (besides the fact that VB doesn't allow this AFAIK).
>I don't know if sequences are such a good thing. They cause a lot of
trouble and code gets messy >if they get too complex. I think you can wor=
k
normally with simple 1 dimensional arrays and >structures.
As mentioned before, if this is how you feel about sequences, then Eu
probably isn't for you. Personally, I find that sequences are the greate=
st
attraction of Eu. Sequences only get as messy if you let them. But this
goes for all aspects of code. In fact, the flexibility of sequences is m=
y
main point when referring to feeling constrained by VB. In Eu, I can
determine what datatypes to keep in which elements and dynamically grow o=
r
shrink sequences much easier than when using arrays in VB. If I don't ha=
ve
a good plan, then yes, the data gets messy, but that's my fault, not the
sequence's. I think it just takes a little discipline
>This is all very logical if you know that only 1 person is developing
euphoria. It should be more >popular, developed by more people.
Well, I think it should be more popular, too, but and the development tea=
m
(which I believe is actually 2 people :) are really separate issues.
Eu will probably never become a mainstream language, although it'd be gre=
at
if it did, but I just enjoy using it too much to abandon it.
Matt Lewis
|
Not Categorized, Please Help
|
|
