[comp.sys.ibm.pc] Turbo C 2.0

psrc@poseidon.ATT.COM (Paul S. R. Chisholm) (10/20/88)

<"He seemed like such a nice man . . . and then he turned out to be a writer!">

In article <182@imspw6.UUCP>, bob@imspw6.UUCP (Bob Burch) writes:
> From Ted Holden at HTE:
(Some screen dumps were included here, which would have been prettier
if the line drawing characters, which had their eighth bits stripped,
had been replaced by '|' and '-' as appropriate.)

> As you can see, the normal built-in debug features which come with Turbo C
> 2.0 are pretty serious.  The stand-alone debugger is for 386 style debugging,
> 486 style debugging, debugging with a second screen, debugging all kinds of
> exotic equipment, exotic screens, cathedral organs running DOS, etc.  Most
> people probably won't ever use it, but, then, you never know.

(Gee, I can't find TD486.EXE on my disk.-)  There are two other big
advantages:  TD leaves more room for the program to run in than TC.
And TD lets you have multiple "views" of the program (stack backtrace,
registers, source code with current statement shown, values of
expressions, etc.) in overlapping windows.  Of course, you get TASM, too.
  
> A quick template of function-key use (which is not provided and possibly
> should be)

Is available by hitting F1 F1, then selecting "Keyboard hot keys".

Paul S. R. Chisholm, psrc@poseidon.att.com (formerly psc@lznv.att.com)
AT&T Bell Laboratories, att!poseidon!psrc, AT&T Mail !psrchisholm
I'm not speaking for the company, I'm just speaking my mind.

rja@edison.GE.COM (rja) (01/19/89)

In article <3717@ttidca.TTI.COM>, hollombe@ttidca.TTI.COM (The Polymath) writes:
> think TC 2.0 supports that mode. (And they still ship on 5.25" disks only.
> They've got some catching up to do).

Simply put.  Not true.  Several people here in Charlottesville  RECEIVED
TC 2.0 on 3.5" microfloppies a while ago.  In fact they received TC 2.0
faster than Borland had promised (apparently Borland thought there might
be a 2 week delay because of the high number of upgrade requests, there
wasn't.  Arrived 3 days after ordering.)

______________________________________________________________________________
         rja@edison.GE.COM      or      ...uunet!virginia!edison!rja  
     via Internet (preferable)          via uucp  (if you must)
______________________________________________________________________________

hollombe@ttidca.TTI.COM (The Polymath) (01/24/89)

In article <1781@edison.GE.COM> rja@edison.GE.COM (rja) writes:
}In article <3717@ttidca.TTI.COM>, hollombe@ttidca.TTI.COM (The Polymath) writes:
}> think TC 2.0 supports that mode. (And they still ship on 5.25" disks only.
}> They've got some catching up to do).
}
}Simply put.  Not true.  Several people here in Charlottesville  RECEIVED
}TC 2.0 on 3.5" microfloppies a while ago.  In fact they received TC 2.0
}faster than Borland had promised (apparently Borland thought there might
}be a 2 week delay because of the high number of upgrade requests, there
}wasn't.  Arrived 3 days after ordering.)

I didn't say you couldn't get TC 2.0 on 3.5" disks.  You just can't buy it
that way in a store.  You have to order it from Borland after you've
bought the 5.25" disks in the store and it will cost you another $15 over
what you've already paid.  Borland also told me it would take two weeks to
get to me (their brochure promised 48 hours).  I made other arrangements.

-- 
The Polymath (aka: Jerry Hollombe, hollombe@ttidca.tti.com)  Illegitimati Nil
Citicorp(+)TTI                                                 Carborundum
3100 Ocean Park Blvd.   (213) 452-9191, x2483
Santa Monica, CA  90405 {csun|philabs|psivax}!ttidca!hollombe

colburn@io.SRC.Honeywell.COM (Mark H. Colburn) (01/27/89)

>I didn't say you couldn't get TC 2.0 on 3.5" disks.  You just can't buy it
>that way in a store.  You have to order it from Borland after you've
>bought the 5.25" disks in the store and it will cost you another $15 over
>what you've already paid.

I just bought a brand new copy of Turbo C 2.0 (professional) and I got it
in 3.5".  The store had both 3.5" and 5.25" versions.  The sales people
there were quite good about making sure that you got the right version of
disks for your system.

I purchased mine in Minneapolis, it could be that they have not gotten them
down in North Carolina yet.  It also could be that your store vendors have
not gotten around to ordering 3.5" floppies yet.

Mark H. Colburn           MN65-2300		colburn@SRC.Honeywell.COM
Systems Administration and Support
Honeywell Systems & Research Center

grumpy@edg1.UUCP (Eric Schwarz) (01/27/89)

Followup-To: scomp.sys.ibm.pc
Subject: Re: turbo c 2.0
Newsgroups: comp.lang.c,comp.sys.ibm.pc
References: <31363@tut.cis.ohio-state.edu> <3717@ttidca.TTI.COM> <3751@ttidca.TTI.COM>

In article <3751@ttidca.TTI.COM>, hollombe@ttidca.TTI.COM (The Polymath) writes:
> 
> I didn't say you couldn't get TC 2.0 on 3.5" disks.  You just can't buy it
> that way in a store.  You have to order it from Borland after you've

This is definitely not true if you're talking about the "Pro" package.
I made the mistake of picking up a 3.5" version at the store and had
to bring it back to exchange it for the 5.25" version.  By the way,
the reason I made the mistake in the first place was the way in which
Borland marks the two versions.  When I picked up the box I noticed
a sticker that read something like "includes 3.5" disks".  Silly me,
I thought this meant that the 3.5" disks were included in addition
to the 5.25" ones.

Eric Schwarz
uunet!edg1!grumpy

mdharding@dahlia.waterloo.edu (Matthew D. Harding) (06/22/89)

In summary of the many responses I received for my Turbo C 2.0 questions,
ssignal.c is provided with 2.0 but not supported. Apparently they include
it just for people who are porting code from UNIX, etc., as a favour. Or
as they say in the manual, "for ease of portation". Portation? Never mind...

As for stat.h, it was in the sys subdirectory (boy am i dumb).

However, I have another question. How exactly do you access the new BGI drivers
in 2.0? I have code that uses the 1.5 BGI drivers, and 2.0 barfs on it. It says
in the manual that the drivers are not compatible, yet I cannot just substitute
the new drivers. Why?

Thanks, Matt.