[OSUNIX-dev] Re: [hpcdev-discuss] Porting open64 to solaris

[Joerg Schilling]

"C. Bergström" <cbergstrom at netsyncro.com> wrote:

> Thanks a lot for letting me know this.. I'm not sure it's something we 
> can send upstream, but maybe the open64 guys can make a suggestion?  I'd 
> much rather link/use maintained code instead of the roll-your-own 
> approach for every missing function.. Almost as soon as snv_107 was 

printf() is a major problem for extended portability of software.
Larger project groups that like to support a high portability level
all seem to have own printf implementations in their portability frame work.
My implementation has the advantage of being cleanly portable and without 
being bound to stdio. In the mid 1980s when other people had problems to
port csh because of it's own stdio-less printf() written in VAX asembler,
it took me 10 minutes to relace the implementation by something portable ;-)

> tagged we started the port.  It's been a TODO item for a while and I 
> actually have license compatible implementations of 
> asprintf()/vasprintf()wasprintf()/wvasprintf() functions.. not to 
> mention they were in libast iirc.. Anyway.. like I said in the other 
> email.. I have to get a new build log so we can hunt for errors and then 

my code is under CDDL.  David Korn has it's own portability world that 
although it is different in many places is based on mainly the same
ideas for portability.

If you e.g. don't know whether a local printf() supports %j %z or %t
you save time in the long run if you have your own printf() with you.


Jörg

-- 
 EMail:joerg at schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js at cs.tu-berlin.de                (uni)  
       joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily