On 02/11/2014 12:52 PM, Marius Liebenberg wrote: > I dont know if this has been asked before but hear me out please. > I wondered why we could not have a number of INI files with an #INCLUDE > type of structure. I would very much like to segment my configuration > into usable sections like all the AXIS tuning parameters in one file for > instance. And then place all the display related stuff into another.
I've occasionally wanted this feature, for example for the hostmot2 sample configs which are identical except for a few variables (the driver name and the board name in HAL). We vaguely follow the already-vague .ini file format, and it does not support this feature. http://en.wikipedia.org/wiki/INI_file I think there's no reason (other than tradition, and manpower) we couldn't invent a new syntax and add this feature to our ini file parser. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
