Re: Euphoria Interpreter design

new topic     » goto parent     » topic index » view thread      » older message » newer message

[Daniel Berstein]

>Before studying Computer&Informatic Engineering (that's the best I can
>transalate my carrer name), I studyied *5* years of Architecture, and I
>*do* know how important analisys and planification is. Before I write a
>single line of code I have a master plan (a blueprint)... a conceptual
>organization rendered on paper, brought from the untangible world of ideas
>to a physical medium. Perhaps some genius programmer espontaneously don't
>need any methology... but the rest of us do. Declaring before using oblies
>you to think twice before coding. There might be exceptions where this
>aproach can lead to some "confusion", but the world is built of rules not
>exception.

Impressive credentials, but I am not really sure what I am supposed to
do with them (I'll look up 'planification' later on in the privacy of
my own bedroom). If it really helps you to scribble on a piece of
paper before you hit the keyboard, that's ok with me too, we are all
different. Unfortunately, you have not answered my question: how
'declare-before-use' enhances readability & conceptual organization.
But, on the other hand, you introduced me to so many big words, I
should be truly thankful. They might come handy one of those days,
when I run out of real arguments.


[Gabriel Boehme]

Sorry, Gabriel, I'll not quote you in full. It is too long, not enough
substance. But I'll deal with some of the points.

First, if I were in a less charitable mood, I would suggest you tried
to muddy the waters with unrelated garbage: uninitialized variables,
invalid subscripts, invalid parameters and the bad habits we
programmers have learned from other programming languages. But I shall
skip that today...blink

You also mentioned 'emotional appeals and verbal attacks' a couple of
times. I am not sure what you meant by 'verbal attacks', but I could
recognize the other one when I read, and I quote: "the willy-nilly way
programmers can do things in QB, C or Cobol." All three prohibited
words in a single sentence - it makes me cry.

And to be quite brutal, your pontifications about Euphoria before and
after routine_id() do not help. Your impractical (your word!) example
is even less useful. (BTW, infinite mutual recursion is not such a big
deal - you blow the stack before you blink. Simple infinite loops are
much worse - unbreakable in pure DOS - and they happen far too often
to me...)

I am glad you have not made up your mind, obviously, which way to
jump. But I am confident you will let us know if you ever do.

jiri

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu