Re: 1 pass?

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

blahblahsnipsnipblahsnip
jiri,lewis,irv said this and the other about chickens and eggs
coming in tops down (woowoo!) and bottoms up (gulp) programming.


i use both. i write my code in almost pure pseudocode,
but structured pseudocode, in one file. that becomes my
.ex or .exw file... i then, in another file(s), at the same
time, write the proc/func's that the pseudocode calls and
that file(s) becomes my .e or .ew file.
benefit? i get jiri's style (and others) of being able
to define my program (problem solution?) in the way
*i think*, and i get the benefit of others who build up
from small snippits of a solution to bigger and bigger
pieces/building blocks of the final puzzle...
by keeping all my routines in include files, and only having
'main' in my .ex or .exw file, i never worry about what
can call what or when or from whence it comes...

hopefully, this approach i use will benefit those with
problems coding in euphoria, and perhaps end the beating
of this horse?

take care, hope this helps--Hawke'

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

Search



Quick Links

User menu

Not signed in.

Misc Menu