On Mon, 11 Jun 2012, Jussi Lahtinen wrote: > > As I see it include is a pre-processing directive. It simply replaces the > > #include statement with > > the contents of an external file. This is a project management > > consideration and not a programming paradigm i.e. OOP, Functional, > > Procedural, etc.. > > > I agree, but I think with OOP, C style #include is obsolete management > choice. > > > > The include statement in C/C++ was intended to allow > > libraries of code to be pulled into the current project. > > > Here is the main point. > In Gambas we already have Extern, Export etc commands for external > libraries, > whether they are written with Gambas, C or whatever. > > > > > > Allowing the developer to split a large project up into smaller, more > > manageable files. > > > > With OOP I don't think you need to do that with files, you do it with > classes. > But maybe someone want to write code with non-OO style. > > > > > > Contrast this to Ada's use of packages. > > > > I don't know Ada, so I cannot say anything it being useful in Gambas. > > > > As for includes, I think this could be a useful tool for some but wonder > > why simply refactoring the program into > > more manageable class' wouldn't give a better solution. IMHO, doing so > > would make the project more maintainable over the long haul.... > > > > I agree. > > > > Jussi > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Gambas-user mailing list > Gambas-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/gambas-user
Hi, I first didn't want to interfere but there recently was a related thread here. Benoît stated back then that only the really needed features will be implemented in the Gambas Preprocessor and scolded me for my proposition to use the CPP instead. Nonetheless, if you really want to use the #include directive and other c-style things in your own dark chamber, nobody would care if you maintain your sources split, merge them via #include and then push them through the gbc3. As indirectly quoted above, it is not a solution for future gambas and I would strongly prefer OO over this but if you need it, why not... Uhh, too late to respond to Randall's last post but I totally recommend his last point. Regards, Tobi ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
