Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!cmcl2!brl-adm!umd5!decuac!felix!chuck
From: chuck@felix.UUCP
Newsgroups: comp.unix.ultrix
Subject: Re: Ultrix 2.0 executable dumps core on 1.2
Message-ID: <13280@felix.UUCP>
Date: Wed, 18-Nov-87 11:56:18 EST
Article-I.D.: felix.13280
Posted: Wed Nov 18 11:56:18 1987
Date-Received: Sat, 21-Nov-87 06:31:02 EST
Sender: chuck@felix.UUCP
Reply-To: pete@tsc.DEC.COM (Pete Schmitt)
Lines: 23
Approved: zemon@felix.UUCP

Reply-Path:

In article <12683@felix.UUCP>, mark@applix.UUCP (Mark Fox) writes:  
> I have a program built on an Ultrix 2.0 system. It executes a new system call
> (getmnt) which didn't exist in 1.2. Guess what happens if I try to execute it
> on a 1.2 system -- it dumps core with the following message and stack trace 
Just like DECs VMS, you don't want to develop programs on newer
versions to run on older versions.  You want to do just the opposite.

	[Actually, with judicious use of logical names and saving of
	appropriate libraries from previous versions, it is fairly
	easy to develop and maintain versions of older applications
	and programs on newer versions of VMS.  I know several
	vendors who do just this; their desire being to support one
	version of the application which is compatable across many
	versions of the operating system.  Alas, even in VMS there
	comes a point where you want to use a NEW feature, and of
	course, you can't go backwards from there and still be
	compatable.  cwv]

-- 
            \\\!///		From: Pete Schmitt
             _   _ 		UUCP: {allegra|ihnp4}!decwrl!tsc.dec.com!pete
           ( Q   Q )		It's okay to say the U... word.
 ---,,,,-------U-------,,,,---