Proc help needed

[Walker]

okay i have 2 procedures but they call on each other so how can i do that because turing nneds to have the procedures above each other but i cant do that as no matter which one i put first it will still have an error, so short of making lots of mini procs how can i do this? is there a way to make turing read both at he same time?

[Delos]

Ah...inter-dependant procedures.

I believe the use of forward can accomplish this:

code:

forward procedure a forward procedure b body procedure a     b end a body procedure b     a end b

I did try this once before, but the environment continually crashed. My best advice in this sit, try to avoid such a sit...it's a helluvalot more to your advantage to not have to make such structures in Turing, seeing as there's a good chance it won't be able to handle them.
But if it can, then go for it! And enjoy...

[Walker]

this forward you speak of, what deos it do? not mentioned in the f10 is it

[AsianSensation]

it's like function prototyping. You can declare the prototype above and have the main body somewhere else. So you can technically call procedures that you have not written a body for yet.

[Walker]

thank you, another question how does this interact with the include command?

[AsianSensation]

nothing?

[Delos]

Include is of a totally different standpoint.

Include is used when one wants to...er...include one file in another. For example, say you have the following code:

code:

put "Hello world!"

and it is saved under world.t.

Then you have another piece of code:

code:

put "is what most ppl like to say when experimenting with programming languages."

saved under like.t

Then you have a third file, let's say thirdfile.t, with the following code:

code:

include world.t include like.t put "And that's how includes work."

The output when you ran thirdfile.t would have all 3 puts. Notice that when you include a file, any extraneous code is automatically processed and/or displayed. The same happens w/ contained code, but as it is contained, it can't go anywhere until it is called.

So, includes are rather handy when you have a bunch of procs in one file, and don't want to copy them directly to another...the best eg. I can think of is if you have one file that has a bunch of procedurized error traps, and you include that file at the header of another file...

...of course this all brings up questions about imports instead...but that's a discussion best left for another time.