🚀 go-pugleaf

In article <6ahlmj$amk$2@janis.virago.org.au>,
Rachel Polanskis <r.polanskis@nepean.uws.edu.au,grove@zeta.org.au> wrote:
>In article <34CB2E71.A180F508@netscape.com>,
>	Jamie Zawinski <jwz@netscape.com> writes:
>> 
>Remember, Linux is still UNIX, and a good programmer will adhere to 
>the paradigms that make a an application portable between UNIX versions.
....
>A good Linux programmer is a portable UNIX programmer.

But these programmers are rare. At least if they learnd UNIX with Linux.

Linux documentation and the Linux include file system makes it hard to become
a good programmer by only seeing Linux code. Most programs that have been
developped on Linux are hard to port to other UNIX flavours.

The main reason for the non-portability of code developped on Linux is that
programmers usually use the wrong include files (those that are only present
for portability reasons and those that are located in the directories
/usr/include/linux and friends). Creating an operationg system that makes it
easy to compile BSD and SYSV derived code is one thing but writing documentation
that allows newbies to learn how to use it is another thing.

A good idea would be if all include files that are only present for portability
reasons have a top comment line that warns to directly include this file.


Joerg

-- 
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) J�rg Schilling D-13353 Berlin
      js@cs.tu-berlin.de		(uni)  If you don't have iso-8859-1
      schilling@fokus.gmd.de		(work) chars I am J"org Schilling
URL:  http://www.fokus.gmd.de/usr/schilling    ftp://ftp.fokus.gmd.de/pub/unix