OpenEuphoria

RE: v2.5 Opens exw files wayyyy too slow

• Posted by Chris Bensler <bensler at nt.net> Dec 24, 2004
• 600 views

Chris Bensler wrote:
> 
> 
> Georg Wrede wrote:
> > 
> > 
> > posted by: Georg Wrede <georg at iki.fi>
> > 
> > > I like the process of:
> > >     Edit -> Run,
> > > Instead of:
> > >     Edit -> Bind -> Run
> > 
> > 
> > > So I buy the binder so that I can now bind everytime I change a file
> > > before I run it.
> > > 
> > > I prefer: Edit - Run
> > > over: Edit - BIND - Run
> > 
> > Now I understand why Euphoria can be blamed for being a hobbyist
> > programming language. If the people who use it run the code
> > after every edit, then they really are hobbyists.
> > 
> > <flame>
> > 
> > In the old days when I had to learn programming, you had to write
> > long chunks of code, check that the logic and content were right,
> > and then get a reservation at the terminal room to punch in your
> > code. We were allowed a maximum of 30min per person per day there.
> > This was because there were only a half dozen paper terminals,
> > and we were some 300 students.
> > 
> > That was hardly the change-one-line-and-rerun method. But we 
> > sure learned to program. Heck, we even had to think in advance!
> > Actually, to many of us now, sitting at the keyboard writing
> > code is not Programming. What we call Programming is when you
> > sit at your desk, drawing data structures or flowcharts or UML
> > on paper or chalkboard while doing Hard Thinking. Or Think
> > while driving or in the shower, or walking the dog.
> > 
> > Only when you've done this Programming, you walk to
> > the computer and punch in the code.
> > 
> > <double flame>
> > 
> > And any nontrivial task gets done sooner and better, and needs
> > less debugging than with the "try-and-retry" method.
> > 
> > I dare say, one never even becomes a good programmer unless
> > one separates thinking and typing.
> > 
> > </double flame>
> > 
> > Now, precisely because the target audience of Visual Basic is
> > the never-get-past-beginner kind of people, VB even checks your 
> > syntax while writing.
> > 
> > </flame>
> > 
> > The speed of Euphoria is perfectly adequate. Period.
> > 
> > Those who call themselves non-hobbyist programmers have used
> > and are using compiled languages in addition to Euphoria.
> > Having got used to them removes the anxiety of a couple of 
> > seconds' wait.
> > 
> > Try this for a change:
> > 
> > Run 
> > -> Think -> Think -> Think -> Type 
> > -> Think -> Think -> Think -> Type 
> > -> Think -> Think -> Think -> Type 
> > -> Run
> > 
> > Sure beats Edit -> Run -> Edit -> Run
> 
> 
> We could all sleep in caves still too :P
> 
> If Euphoria would return all parser errors at once, what you are saying 
> might be more acceptible.
> 
> However, interpeted programming is not quite the same as compiled 
> programming.
> With compilers, you have extensive error reporting, and a heavy duty 
> debugger, and a degree in computer science to be able to use them 
> effectively.
> 
> You are right in that people should be planning before they code, but I 
> don't know anybody that plans mistakes.
> 
> Chris Bensler
> Code is Alchemy
> 

I should add:
Why is it do you think that almost every compiler (actually every one 
I've ever seen) returns as many errors as it can, even if those errors 
are cascaded?
Also, why is that almost every compiler has a highly advanced debuggger?

The answer is: so that you don't have to spend so much time in 
compilation. Granted nowadays with faster machines, compilation time is 
not as big of a concern anymore.

Chris Bensler
Code is Alchemy