Add xdr support

Christopher Faylor
Sun Feb 14 19:06:00 GMT 2010

On Sun, Feb 14, 2010 at 05:36:45PM +0000, Dave Korn wrote:
>On 14/02/2010 05:46, Charles Wilson wrote:
>> Dave Korn wrote:
>>> On 13/02/2010 23:53, Charles Wilson wrote:
>>>> IIRC at that time Corinna suggested that newlib was the appropriate
>>>> place for this, if I wanted to contribute it post-1.7.1. 
>>>> I asked how to
>>>> go about adding something to newlib that might not work for all targets,
>>>> and she said:
>>>> Unfortunately, my google-foo is not strong enough to find that message
>>>> in the cygwin archives, 
>> I bow to your superior google-foo. 
>  I just went from the first post you listed to the thread view and read all
>the followups.  More like mechanical turk version of a search algorithm than
>any kind of google-fu on my part!
>  ObTopic: I think newlib would be a nice place to put this functionality,
>particularly since you've already gone to the trouble of fitting it into the
>framework.  It's entirely plausible that the newlib linux targets would find
>this code useful as well.  "Small embedded system" doesn't mean "not
>network-connected" any more these days, not by a long way, so I think it is a
>suitable and appropriate thing to propose adding to newlib.

You could make the same argument for much of the functionality we've
added to cygwin.  I'm sure a significant number of functions could be
added to newlib if we were so inclined.  Just take a look at the libc
directory or the regex directory.

One of my problems with newlib is that, once this is added, you'll need
to get permission from Jeff J. for any future modifications - with all of
the bottleneck potential that involves.  The other problem is that you
potentially have to deal with the other truly embedded projects which
use the library.  They sometimes have objections to the way things
are implemented.

(And I hate having to use _DEFUN in the year 2010)

And, although it doesn't apply in this case, if I was Red Hat, I'd be
leery about allowing major new functionality into newlib because it
dilutes their Cygwin ownership.  How can you claim to own something like
Cygwin when a major amount of the code is added and modified without a
license assignment?

I understand why, from a purist's point of view, someone might think
this belongs in newlib.  I just think that adding things to newlib
means more hoops to jump through for the Cygwin project.  I'm more
concerned about that than I am about newlib's project definition.

All of that said, however, I'll leave it up to Chuck.  I assume that
since he's already done the work for newlib it would be a lot of extra
work to get this into Cygwin.  I'm not going to offer any objections
if this gets accepted to newlib.


More information about the Cygwin-patches mailing list