Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site tesla.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!houxm!vax135!cornell!tesla!mac From: mac@tesla.UUCP (Michael Mc Namara) Newsgroups: net.lang.c Subject: Re: C portability between non-UNIX operating systems. Message-ID: <438@tesla.UUCP> Date: Fri, 19-Oct-84 12:40:51 EDT Article-I.D.: tesla.438 Posted: Fri Oct 19 12:40:51 1984 Date-Received: Thu, 25-Oct-84 03:55:38 EDT References: <2208@pur-ee.UUCP> <85@decvax.UUCP> , <226@boulder.UUCP> Lines: 32 > In article mac@tesla.UUCP (Michael Mc Namara) writes: Organization: Cornell Electrical Eng. Lines: 29 > > > > [2] The biggest problem I have found is that they don't call > >stdio.h stdio.h!!!! On VMS, it is invoked with #include > >on the Harris, it is "STDIO.H" (caps necessary), et cetera > > > > > [3] Vms requires everything be initialized if it is to be external. > > Really? Which compiler do you use? The VAX11 C (trademark of DEC, I'm > sure) compiler (1) understands as well as other nifty things > like and that one would expect to be UNIX (TM) > dependant. Furthermore, externals do NOT need to be initialized. > > My experience has been that UNIX code ports to VMS with little trouble, > unless (1) you wire file names, or (2) use lots of process/job control > stuff that VMS does not support. > > x|p| |p~ |p|g|pp|g|`|g|x|p|pp|g|g|`~||p|pp| ~ p||| > Jon Corbet > National Center for Atmospheric Research, Field Observing facility > Ok, after I read your article I walked over to the Vax11 computer system we have here at Cornell, and indeed, they are not running Dec's C but are running Whitesmith's C for the Vax11, hence the problems are not due to VMS but to the particular compiler written by Whitesmith.... Michael Mc Namara @ Cornell University.