Hi Peter,
I have not encountered a problem with multiple do's. I don't see why there
should be a problem.
If your functions in test_opcodes.r evaluates anything that ultimately
attempts to evaluate words defined in ea.r, then you would be getting an
error message, if ea.r had not been do'ne.
My guess is your problem has nothing to do with 'do.
Send me your files off list and - quite likely - I'll have a solution for
you soon.
mailto: [EMAIL PROTECTED]
At 04:45 PM 6/15/00 +0200, you wrote:
>Hello!
>
>A couple of weeks ago I asked how to split a
>project in to several files. The solution was
>to 'do' all files to include them in the
>main file.
>
>This has worked fine until now...
>
>I now have created some files like:
>
>opcodes.r (includes a 'do %ea.r')
>ea.r
>test_opcodes.r (includes a 'do %opcodes.r')
>test_ea.r (includes a 'do %ea.r')
>
>In the test_* files I have prepared test cases
>to verify the functions in the other files.
>
>Executing the test_ea.r file is working fine and
>will call all functions in ea.r without problems
>but when I execute test_opcodes.r it does not
>execute the functions in ea.r. There are no error
>messages saying that no function by that name
>is found.
>
>Is there some sort of limit to how 'deep' a
>function call could be?
>
>I have tried to include a 'do %ea.r' in the
>test_opcodes.r as well but nothing changes.
>
>Could someone please help me?
>
>Best regards,
>Peter Carlsson
>
>----------------------------------------------------------------
>Peter Carlsson Tel: +46 31 735 45 26
>Saab Ericsson Space AB Fax: +46 31 735 40 00
>S-405 15 G�teborg Email: [EMAIL PROTECTED]
>SWEDEN URL: http://www.space.se
>----------------------------------------------------------------
>
>
>
;- Elan [ : - ) ]
