Totally modular, dude \m/ :P

[Anonymous]

hey now i know to use modules. My next question. How the freak do I pass control to one? thanx.

[na_th_an]

You can't pass control to another module. You just call its subs and functions.

[Nexinarus]

pretend a module is a library, but you can share variables aswell.

[Zack]

So fill me in here. I gotta get into this fun...
You make SUBs and FUNCTIONs and whatever other declarations/variable assignments you want, and then '$INCLUDE them?

[na_th_an]

Read my tut about it: http://faq.qbasicnews.com/?blast=PushingTheLimitsOfQb

Basicly you have a main BAS file with a main section (outside subs) and SUBs and FUNCTIONs as well. The you add more BAS files that only contain DIM SHAREDs, COMMONs, TYPEs and more SUBs and FUNCTIONs. To make those SUBs and FUNCTIONs visible from another module (your main module, for example), you have whether to:

1.- Add the DECLAREs to the module you want to call extern SUBs of FUNCTIONs from.

2.- Stuff all the DECLAREs in a BI file and '$INCLUDE it in the module you want to call extern SUBs or FUNCTIONs from.

What I do is having a different BI file for each module I have, that way I '$INCLUDE just what I need. I think it is cleaner

[oracle]

No code in any module other than the module you set as the main module will be executed, unless it is a SUB or FUNCTION and you have called it from the main module.

To change the main module, turn full menus on and look in the Run menu.

[Zack]

Cool, I never saw that before.

[Anonymous]

hey thanx nath now alls i gotta do is remember where in the XMS i put all my data ;p

oh, btw i have another question!!

lets say i redimmed an array Tile(130) as integer

ok, now lets say i moved to another module, but i didnt share the array.

what happens if i point to it from the other module? cha0s?

[adosorken]

cha0s.

If your array isn't SHAREd across modules and isn't passed as an argument (oi!!!), it won't be available to a function in another module.

[Jark]

What I like in Nathan excellent tut is that it insists on the fact that shared variables are really tricky to control with the modular approach.

Based on my experience with the TC-Lib and TC-Ray, where I used a lot of shared and common shared stuff, I think I will come back to the "observers" and "modifiers" logics in the future versions.

I think sending and receiving parameters from module to module, through subs that don't do anything but transmitting these parameters, is an excellent solution (though it can also lead to saturating the stack if there are too many local variables...).