On Tue, Mar 05, 2013 at 11:44:37AM +0100, Marco van de Voort wrote: > In our previous episode, Henry Vermaak said: > > > >>But on the other hand, if an application programmer could > > > >>disable FPC's unit handling and use make -j instead, choosing > > > >>to pay the price of difficult maintenance, it might defuse the > > > >>criticism coming from certain quarters. > > > >> > > > >Make can not figure out the dependencies between units by itself > > > >as it would need to parse them. > > > > > > That's for the user to do, if he thinks he can do a better job than FPC. > > > > Or implement an option that spits out the dependencies for make, so that > > the user doesn't have to do this. > > That does't work, since in FPC an unit is an interface AND an > implementation. And inline functions are in the implementation, not the > interface. > > The only way is to simply toss the modular system (units) out, and work with > $i, declare functions as externals in headers, let the compiler spit out > dependencies.
OK, I'll drop this line of enquiry then :) Thanks for the information (and the patience). Henry _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel