Modules are namespaces with the exception that the default namespace consists of all imported modules merged with the current program's namespace. The default behavior happens to be to import all modules, unless you use the Framework keyword. This is why at first glance BMax doesn't appear to have namespace support.
This is actually very similar to how Delphi (Object Pascal) handles it's concept of namespaces, "units". Delphi just doesn't import everything available by default.
Even with several module's identifiers imported into the main namespace, it is still possible to access any overlapping identifiers explicitly by their module "path", or namespace as Ziggy pointed out.
Modules are declared under the mod folder in a particular place directory structure ("mod/ModuleScope.mod/ModuleName.mod" where ModuleScope is your company name and ModuleName is the name of the module, obviously) and begin with the keyword Module:
This is actually very similar to how Delphi (Object Pascal) handles it's concept of namespaces, "units". Delphi just doesn't import everything available by default.
Even with several module's identifiers imported into the main namespace, it is still possible to access any overlapping identifiers explicitly by their module "path", or namespace as Ziggy pointed out.
Modules are declared under the mod folder in a particular place directory structure ("mod/ModuleScope.mod/ModuleName.mod" where ModuleScope is your company name and ModuleName is the name of the module, obviously) and begin with the keyword Module:
Module ModuleScope.ModuleName