1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59
|
includefile(modules/intro.yo)
COMMENT(
intro - what/why are modules? Benefit: not just header handling, also
extra level of aggregation
available? a bit wip
)
sect(An initial, complete module)
includefile(modules/initial.yo)
subsect(Using a module)
includefile(modules/using.yo)
lsect(COMPOD)(Module interfaces and implementations)
includefile(modules/implementations.yo)
subsect(Module interface units);
includefile(modules/interface.yo)
subsect(Using the 'components' module)
includefile(modules/usecomponents.yo)
subsect(includes and using namespaces)
includefile(modules/includes.yo)
subsubsect(module specific imports and #includes)
includefile(modules/modincludes.yo)
lsect(PARTITIONS)(Module partitions)
sect(modiles/partitions.yo)
(PRIVMOD)private module partitions?
lsect(HDRIMPORT)(Importing headers)
sect(modules/headers.yo)
lsect(MODMAPPER)(Specifying gcm.cache locations)
namespaces in modules
header files:
existing headers (like iostream)?
own headers?
-fmodule-header flag and then import
what's visible? Same function names in differnt modules? -> namespace required
namespaces are independent from modules: defining module-specific
namespaces is OK
constructing a modules library
lsect(MODDESIGN)(Designing programs using modules)
includefile(modules/design.yo)
|