From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Tue, 3 Sep 2002 04:36:57 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 317 ************************************************** Monday 02 September 2002 Number 317 ************************************************** Subjects for today 1 Re: Some packages : Andreas Buening **= Email 1 ==========================** Date: Tue, 03 Sep 2002 23:27:25 +0200 From: Andreas Buening Subject: Re: Some packages Stefan Neis wrote: > > On Sun, 1 Sep 2002, Andreas Buening wrote: > > > larger executables but this won't really hurt us. I propose to > > use those extensions, put all of them into one lib ux2 and > > just use -lux2 for every package we have. > > At least, it should be a different name, I suppose, otherwise > there might be a clash later. Ah, this means Holger is really going to build _ux2_.dll? [snip] > > One of the reasons why Linux is that successful is because of > > the philosophy "if there is a problem fix it". If a function > > /option is missing somebody adds this feature. End of story. > > Yes. But you still shouldn't mix BSD and GNU library functions > in the same library, that was my point. Of course, it would > make perfect sense, but FSF doesn't allow it. Pu GNU stuff in > a different DLL, that's what I was getting at ... If you mix BSD and GPL the result will be GPL. ;-) > > You could just add those functions to the emx dlls without > > hurting the backward compatibility. So why don't we do it? > > IMHO, modifying EMX dll's is EM's prerogative.... emx is GPL, this means everybody can take the code and release an extended emx library. The question is whether it makes sense to do so if EM doesn't want to extend his libs. I guess, not. > I could create a cExt.dll from my Posix/2 library, if people are > interested ... What I exactly mean is that we have a ux2 or unixos2 or emxext or whatever library that contains everything that a) used to be in other libraries like glibc, b) is not in emx, c) is not supposed to be a standalone library (like gettext is), d) it is used by at least one UnixOS/2 package. An example: I want to add regex to our unixos2 library. There is a new regex library written from scratch by an IBM employee. It supports wide characters, or to be exactly it _would_ support wide characters if emx _had_ support for it. The header files wchar.h and wctype.h are required. According to my "Programming in C" book these header files are now part of Standard C. So my question would be: Are these header files and the according functions part of Posix/2? If yes, take them and put them also into the unixos2 library package. If not, find another libc (glibc, bsd libc) that contains those headers and take them. Those string functions shouldn't need too much changes before we can use them. Finally, I want to get rid of those annoying #ifndef __EMX__ /* do some real stuff */ #else /* do some dummy stuff */ #endif statements. Even if e.g. some locale support doesn't work correctly we can write code as if we had a full featured libc. bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Mordor where the Shadows lie.