[PATCH] memmove

[Sascha Schumann <sa...@schumann.cx>]

    Hi,

    this patch allows us to build on platforms which lack
    memmove. Note that acconfig.h must be added to the CVS before
    you commit the changes.

-- 

          Regards,

                            Sascha Schumann
                                 Consultant

Re: [PATCH] memmove

[Sascha Schumann <sa...@schumann.cx>]

On Mon, Dec 27, 1999 at 06:14:30AM +0100, Life is hard, and then you die. wrote:
> 
> >     this patch allows us to build on platforms which lack
> >     memmove. Note that acconfig.h must be added to the CVS before
> >     you commit the changes.
> 
> While this patch is minor, it begs the question: how much effort should
> go into supporting non Ansi-C systems?

    Ah, rhetorical questions. How I love them. :)

    Let's rewrite your question:

    Where do you want to draw the line between supporting an OS
    and dropping support for it? 
    
    I think it makes sense to support pre-ANSI-C systems*, if it
    takes little effort to do so. That is the case, if the effect
    of the required changes is minimal. 

    Also note that with Apache 2.0's autoconf system we support
    features, not operating systems. The autoconf system does not
    depend on hardcoded values for each supported operating
    system. It detects features and provides replacements for
    missing features. This is the key to real portability.

    * the pre-ANSI-C toolchains are hardly comparable to the ones
      used today. Often GNU tools are the only choice to do
      something productive on these systems.

-- 

          Regards,

                            Sascha Schumann
                                 Consultant