psrc@pegasus.ATT.COM (Paul S. R. Chisholm) (05/19/90)
In article <306@caslon.cs.arizona.edu>, ckindel@cs.arizona.edu (Charles E. Kindel, Jr. [Tigger]) writes: > The press release doesn't mention Windows support! It was my understanding > that Turbo C++ would provide this. Is it an oversight in the PR or are > we Windows programmers still being ignored by Borland. Nope, Turbo C++ 1.0 and Turbo C 2.0 still don't support MS Windows. I haven't heard anything official (or unofficial) from Borland, but they've made general statements that they're moving toward Windows compatibility. (I'm sure Walter's glad to hear this.-) Paul S. R. Chisholm, AT&T Bell Laboratories att!pegasus!psrc, psrc@pegasus.att.com, AT&T Mail !psrchisholm I'm not speaking for the company, I'm just speaking my mind. I have no relationship with Borland except as a happy customer (but then again, I'm not writing MS Windows applications.)
bobmon@iuvax.cs.indiana.edu (RAMontante) (05/25/90)
Re: the v2.0 __STDC__ fluke. Either this was fixed by posted patches or recent releases have it fixed (probably both). My copy has no problem with it when I force "ANSI keywords only".
wolf@ariel.unm.edu (Mark Giaquinto) (05/26/90)
I tried to find the orginal article to reply to, but I couldn't so here I go. In article jjohnson@urbana.mcd.mot.com (Jeff Johnson) writes: >My Borland source looked into the missing main() problem: >] From: darcy@druid.uucp (D'Arcy J.M. Cain) >] Subject: Does Borland consider main an extension to ANSI? >] I just thought that this was so weird I wanted to share it. I have the >] following program. >] #include <stdio.h> >] main() { printf("STDC is %d\n", __STDC__); } >] Compiled under GNU C I get the following expected output: >] STDC is 1 >] Compiled under Turbo C 2.0 I get an error that __STDC__ is not defined. >] I compile using the -A switch (disable all non-ANSI extensions) and the >] program compiles but the linker complains that there is no main function. >] Looking at the assembler output confirms this. So what's up? > I checked the program in the note about __STDC__ and at > least in TC++ 1.0 there is no problem. Since I don't have a > copy of TC 2.0 anymore, I can't check it. >This is not much help I suppose, but it is a reason to upgrade. 8-) >-- >Jeff Johnson +1 217 384 8542 Motorola Inc On page 239, User's Guide, Turbo C 2.0 it states the following: "__STDC__ The constant 1, if you commpile with the ANSI compatibility (-A) flag (ANSI Keywords Only ... ON); otherwise the macro is undefined. Compilied the program with the "-A" and it ran fine. I hope this helps. -- Winter Wolf (aka Mark Giaquinto) wolf@ariel.unm.edu 669 Black Hawk Dr NE, Albuquerque New Mexico 87122 "All of us get lost in the darkness, Dreamers learn to stear by the stars." -- Rush
malloy@nprdc.arpa (Sean Malloy) (05/26/90)
In article <4776@pegasus.ATT.COM> psrc@pegasus.ATT.COM (Paul S. R. Chisholm) writes: >In article <306@caslon.cs.arizona.edu>, ckindel@cs.arizona.edu (Charles E. Kindel, Jr. [Tigger]) writes: >> The press release doesn't mention Windows support! It was my understanding >> that Turbo C++ would provide this. Is it an oversight in the PR or are >> we Windows programmers still being ignored by Borland. > >Nope, Turbo C++ 1.0 and Turbo C 2.0 still don't support MS Windows. >I haven't heard anything official (or unofficial) from Borland, but >they've made general statements that they're moving toward Windows >compatibility. PC Week indicates that there is a version of TC++ in-house that has Windows support; no dates for release are available yet -- it's probably not even to beta. | "The three most dangerous Sean Malloy | things in the world are a Navy Personnel Research & Development Center | programmer with a soldering San Diego, CA 92152-6800 | iron, a hardware type with a malloy@nprdc.navy.mil | program patch, and a user | with an idea."