OpenEuphoria

Re: 1 pass?

• Posted by Ad Rienks <Ad_Rienks at COMPUSERVE.COM> Aug 08, 1998
• 605 views

Michael Pallfry,

Your idea looks good, but IMHO it is not necessary to write a seperate
Euphoria program for it. If you want to do it your way, you could write
your program in a subdirectory, and include main.e, interface.e, sound.e
etc. All these include files should then have global routines and
variables. If the program works you could concatenate all those files aga=
in
into your main program. Using ed.ex or Cuny=B4s editor you can have all f=
iles
open at the same time and work alternating with them.

Regards,
Ad Rienks

original message

From: mike <michael at IGRIN.CO.NZ>
Subject:      Re: 1 pass?
To: EUPHORIA at cwisserver1.mcs.muohio.edu

Hmmm..., why doesn't someone just write a simple editor similar to Mike
Carrolls. But instead of having a tab for each separate file open, have
(user-definable) tabs representing various groups of  subroutines for a
single open file ?  The labels might be perhaps, say, Main  Fileops
Interface  Sound
I suppose that the actual file would have to a Eu sequence and some minor=

details about opening/closing the file would need resolving etc..But, onc=
e
operable such an editor would enable a programmer to code any way they
desired. Some things to keep in mind would probably be that when testing
code the text sequence generated to invoke the EX/EXW executable would ne=
ed
to be in the "Standard" Eu format, ie: main() at the end and or_all() etc=
=2E.
at the start. Some rules might be that any routines within each group tha=
t
call each other be Std_Eu and any inter-group links do the same - I suppo=
se
that (apart from the "top-level") the order that a pure text file of code=

be created (for testing etc..) be as in the above example:

Fileops
Interface
Sound
Main

Now, when someone programs this in Eu, can I please have a copy?


Yours Truly
Michael Palffy

michael at igrin.co.nz