XIncludeFile "filename.pb" As ModX

[the.weavster]

As an alternative to the verbosity of

Code: Select all

DeclareModule ModX
;...
EndDeclareModule

Module ModX
;...    
EndModule

How about:

Code: Select all

XIncludeFile "filename.pb" As ModX

And then a naming convention to determine which procedures/variables in filename.pb are public and which are private so it doesn't have to be explicitly stated.

[Bisonte]

I agree

But there is one question :

If there is no DeclareModule/EndDeclareModule block... how the compiler knows what is private and public ?

Or have I misunderstood .... ?

[the.weavster]

If there is no DeclareModule/EndDeclareModule block... how the compiler knows what is private and public ?

I suggested a naming convention. One possible option for example:

Code: Select all

Procedure MyPublicFunction()

EndProcedure

Procedure my_private_function()

EndProcedure

So if the compiler finds a procedure name starting with a lowercase letter then it's private otherwise it's public.

I hate having to bother with Declares

[Mistrel]

Conventions should not necessarily be standards. For example, I define my private functions with a preceding underscore.

[freak]

An explicit public interface and a clear separation between definition & implementation encourage better information hiding which is the main purpose of modules. Usage of implicit conventions is rather counter productive in this regard.