OpenEuphoria

Re: version of euphoria ZIP

• Posted by Vincent <darkvincentdude at yahoo.com> Nov 06, 2005
• 453 views

Juergen Luethje wrote:
> 
> Vincent wrote:
> 
> > Juergen Luethje wrote:
> 
> <snip>
> 
> >> So your code clearly is less readable and/or less maintainable than
> >> "normal" code. While you are of course free to do what you want
> >> privately, obviously this way of writing code cannot be recommended in
> >> general.
> >
> > My code is very easy to read and maintain, simply using some machine
> > specific routines w/ comments isn't going to make my code any less
> > readable.
> 
> For most people it's not hard to understand that code such as
>      machine_proc(64, 3)

machine_proc(64, 3) -- sleep
machine_proc(SLEEP, 3)

Those are pretty readable to me.

> is not good readable. And I had told you about well known potential
> problems concerning comments, but I learned that you believe you are the
> only person on this planet who is "immune" to certain mistakes.

Do you ever mistake 2+2 for being 5? Probably not. Do you forget how to spell
your name? Probably not. Do you forget how to get to work everyday? Not usually.
Do you forget how to drive? Not if you do it all the time.

My point is these common activities become automatic, where you dont have to
think about it, you just do it. In my case this also goes for adding and/or
modifing comments next to certain pieces of my code.

> > You know we can debate about this for centuries, but in the end we're
> > just gonna do what we want anyway. Obviously effeciency is not top
> > priority for you, but that is quite ok.
> 
> This is not "obvious", but false and a simplistic statement.
> Writing efficient code does not just mean using some machine specific
> routines with comments. You might want to read the Euphoria
> documentation carefully, in order to learn more about writing efficient
> code.

Well excuse me, when did I *ever* imply that using machine specific routines is
the only way to improve program efficency? One of the most important factors in
determinding efficency has to do with the algorithms one develops.

FYI sir, I have read the Euphoria documentation several times, and overlook
perform.htm/doc tips with everything I do in Euphoria.
 
> For instance I use profile and profile_time to examine programs.
> Depending on the program, there are several ways to make it more
> efficient. Sometimes I write parts of a program in assembler.

I suppose peeking & poking machine code is easily readable too, correct?

> Regards,
>    Juergen


Regards,
Vincent