Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!columbia!cunixc!nwc
From: nwc@cunixc.columbia.edu (Nick Christopher)
Newsgroups: comp.sys.ibm.pc
Subject: ** Re: MSC 4.0 Large Model ** Original Posters problem solved!!!
Message-ID: <72@cunixc.columbia.edu>
Date: Wed, 19-Aug-87 16:59:26 EDT
Article-I.D.: cunixc.72
Posted: Wed Aug 19 16:59:26 1987
Date-Received: Sat, 22-Aug-87 04:26:03 EDT
References: <10400006@altger.UUCP>
Reply-To: nwc@cunixc.columbia.edu (Nick Christopher)
Organization: Columbia University Center for Computing Activities
Lines: 44


Yes I started the whole thing :-)  And I am glad to announce my code runs!!!!!


I pulled from all the answers to my question and these were the key
ingredients:

	1) Use NULL not 0 as often as applicable.

	2) use sizeof()'s in malloc()'s and calloc()'s i.e.:
		
  		char *s,*s2;

		s2 = "hello";
		s = malloc(strlen(s2)+1);
		strcpy(s,s2);

	  This is will slide through on a VAX but "don't try this at home
	  kiddies", instead:

		s = malloc((strlen(s2)+1)*sizeof(char));

	3) Make a ".h" file and externally declare ALL your functions
	   so that the return type is clear before a function it called.

	4) Compile with the -DLINT_ARGS an clear up all the messages
	   generated. I had problems with free(foo) when foo was a pointer
           to a structure, free((char *)foo) solved the problem.

Actually all of these are basic good programming habits, I was just ignored
them since the VAX 8700 I was on was so forgiving.... It served me right!

Again, thanks for all the replies to my query, they made the difference.
In the imortal words of Bartles&James, "And, Thank you for your support!"

/nwc


		
-- 
		"I am the Lorvax. I speak for the machines."
______________________________________________________________________________
nwc%cunixc@columbia, seismo!columbia!cunixc!nwc  BITNET: nwcus@cuvma 
            USENET: (seismo | topaz)!columbia!cunixc!nwc