Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!mordor!lll-tis!ames!sdcsvax!nosc!cod!murphys
From: murphys@cod.UUCP (Steven P. Murphy)
Newsgroups: comp.lang.c
Subject: Re: Stack overflow with MSC V3.0
Message-ID: <736@cod.UUCP>
Date: Wed, 24-Jun-87 12:05:25 EDT
Article-I.D.: cod.736
Posted: Wed Jun 24 12:05:25 1987
Date-Received: Fri, 26-Jun-87 05:26:53 EDT
References: <YUo0hEy00VsGy9c0=e@andrew.cmu.edu> <199@sugar.UUCP>
Organization: Naval Ocean Systems Center, San Diego
Lines: 18

In article <199@sugar.UUCP>, peter@sugar.UUCP (Peter DaSilva) writes:
> In article <YUo0hEy00VsGy9c0=e@andrew.cmu.edu>, mc35+@andrew.cmu.edu (Mark Chance) writes:
> > > ... but on the pc I use:
>                    ^^
> > >
> > >		    > msc /AL /FPi  filename
> > >		    > link /STACK:65000  filename
> > >
> > > and all I get is stack overflow. 
> 
> Why are there postings about IBM-PC specific problems in a generic 'C'
> group? Isn't there a comp.sys.ibm-pc group? Not all of us have systems
> limited by intel's militant segmentism, and some of us had hoped to avoid
> it by 'ug'-ing ibm and intel specific groups.


The original question was one of portability.  It ask why a program 
that would compile fine in a UNXI environment would bomb in a micro envrionment even when general allowances were made for compiler differences.