On Thu, Mar 15, 2007 at 05:22:19PM -0400, Russ Nelson wrote:
> Fabio Busatto writes:
> > Otherwise, how do you suggest to make various new features
> > available on-demand at compile time?
>
> The exact method is dependent upon the exact code, but most generally,
> you provide a library of functions, some of which have the exact same
> API, and then you link to one or the other depending on which feature
> you want. Think "object-oriented programming" only done efficiently
> at compile-time (or, more properly, link time).
We're not discussing on software development, but on qmail evolution using
a patch system that lets the user to decide if a patch must be included in
the final binary.
Your answer is not concrete, and maybe I'm too limited in programming
concepts but I cannot understand how it could be a solution for our problem.
Adding APIs should imply that you permanently modify the original source code:
how can you let the user to compile the original code if your APIs are in?
> #ifdefs are the bane of a programmer's existance. A professional
> won't use them.
Sure? Are you really sure? You're saying that about every software (including
djb's one and the main os kernels and are written by novices.
I can accept the sentence "I don't like preprocessor directives", but not
"A professional won't use them".
I seldom use #ifdef when I create a new software, but this is another case,
we're not creating a new software, we are creating a patching system for an
existing project.
Please clarify me how can you approach our problem (not a generic programming
issue) with your solution.
I'm really interested, not just flaming, but I need some concrete examples of
what you think, because I really cannot understand your mind.
Finally, about oop (without creating a fight on it), I cannot undestand how
can it be done if one of our project goals is to keep the djb's programming
style (that's all but object oriented).
Maybe I just misunderstood your approach, but I want to be really sure of my
choices before starting.
Sorry, but your solution is not applicable in this context, or I'm not able
to understand how. If you really want to help me, please provide some example
that let the user to obtain the original qmail code or a fully patched one
in a better way simply switching something at compile time.
Bye
Fabio
|