[Info-vax] Looking into C-include files on VMS

[Joerg Schilling]

In article <00A944D0.32BE9C1D at SendSpamHere.ORG>,
 <VAXman-  @SendSpamHere.ORG> wrote:

>Exactly!  That's why the effort is called "porting" and not "compiling and
>linking".  If there is something that doesn't exist to support the feature,
>the person "porting" the code needs to redesign/recode that portion of code.
>The end results should be the same.  Get the fork out of there and rewrite
>the code to work with some other scheme supported in the OS.

How much code did you port already?

Decently (portably) written software just needs a recompile if this is done
on an OS that follows standards.

Problems usually arise if an OS supports interfaces that use well known names
but does not implement the well known funktionality with these interfaces or
if interfaces are implemented in an incomplete way.
Let me give you examples:

-	An inttypes.h that does not define maxint_t is a portability problem

-	A vfork() that does not behave like vfork is a portability problem.

-- 
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