J Jost aus Soest Active Member Licensed User Longtime User Mar 27, 2012 #1 When I'm reusing an utility-module, I'm often forgetting to activate the libs used by this module... So it would be nice to have something like an "auto-bind-feature" controlled by code, e. g. using a declaration like this in the reused module: Code: Uses Reflection, Threading Also a kind of compiler directive as comment would be possible, e. g.: Code: '$Uses Reflection, Threading In future, everytime I import such a module in a new project, the libs are "automagically" binded i. e. activated.
When I'm reusing an utility-module, I'm often forgetting to activate the libs used by this module... So it would be nice to have something like an "auto-bind-feature" controlled by code, e. g. using a declaration like this in the reused module: Code: Uses Reflection, Threading Also a kind of compiler directive as comment would be possible, e. g.: Code: '$Uses Reflection, Threading In future, everytime I import such a module in a new project, the libs are "automagically" binded i. e. activated.
NeoTechni Well-Known Member Licensed User Longtime User Mar 27, 2012 #2 That's ingenious actually. Especially if it gets b4a to download a lib the user doesn't have
