Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!osu-cis!att!mtunx!lzaz!bds
From: bds@lzaz.ATT.COM (BRUCE SZABLAK)
Newsgroups: comp.sys.atari.st
Subject: Re: Mark Johnson C
Message-ID: <155@lzaz.ATT.COM>
Date: 17 Jun 88 11:54:16 GMT
References: <8806162102.AA01677@ucbvax.Berkeley.EDU>
Organization: AT&T ISL Middletown NJ USA
Lines: 23

In article <8806162102.AA01677@ucbvax.Berkeley.EDU>, nfrech@ALMSA-1.ARPA ("Norman R. Frech") writes:
> 
> Has anyone out there had any experience/luck with Mark Johnson C.

Yes, I've had v2.0 for a week or 2, and I've compiled one program in
excess of 1700 lines or so with no problem. I'd like to help you but
your problem description is pretty vague (but not more so than some MR's
I've received ;-) ).

Remember: MJC (and MWC) have 16 bit ints and 32 bit pointers which cause
99% of all porting problems in my experience. Run LINT on your vax code
and look for mismatched pointer assignments and inconsistent use of
parameters to functions (Mark: any chance of supporting function
prototypes ala ANSI?).

If that fails, take a shot at sprinkling some printfs in your code
to insure your getting into main ok and so on. Look through your code to
see if any kind of error will cause you to exit early.
As a last resort, compile your program one function at a time and test:
compile main (commenting out function calls in it), then the next
function etc.

Good Luck.