agollum@engr.uky.edu (David Herron aka Admiral Gollum) (10/14/87)
Hello,
I just received Borland's Turbo Pascal 4.0 upgrade offer and I thought I
should post it in case anyone misses Borland's small, obscure ads :-) :
Turbo Pascal 3.0 (any version--CP/M, for instance) may be upgraded for
$39.95 and the serial number from your old disk(s). The various toolboxes
may be upgraded under similar terms. A "Developer's library" consisting of
all of the toolboxes and the Turbo Pascal Tutor may also be ordered with
the compiler for $150.00. All programs are available on 5 1/4" and 3 1/2"
disks.
TP 4.0 has these new features:
Separate interactive and command-line (with MAKE) compilers. The
built-in editor supports 43- and 50-line screens, colors, and tabs. The
editor remembers the last 8 files edited--you may return to any of them at
the correct cursor position, with the correct search string/options. The
output screen may be saved while debugging. Generation of .BAK files may
be suppressed (yay!).
The one-pass compiler now produces .EXE files, with .MAP files for
debugging. 80x87 support is built-in. They claim 27,000 lines per minute.
The compiler now allows short-circuited boolean expressions; the linker can
now remove unused code and link in .OBJ files. The command-line compiler
runs in 256k and the interactive environment in 384k. The interactive
compiler still dumps you into the editor after the first editor.
Data types: Byte (0 - 255), ShortInt (-128 - 127), Word (0 - 65535),
Integer (-32768 - 32767), LongInt (-214783648 - 2147483647), and IEEE Real
(+/-1E-38 to +/-1E+38). Boolean, char, scalars, subranges, Strings,
arrays, sets, files. Reals may be Single, double, extended, or "Comp."
Static variables may use up to 64k; dynamic variables may use any amount.
"Device-Independent" Graphics support for CGA, MCGA, EGA (64k, 256k,
monochrome), VGA, Hercules, AT&T 6300, and 3270 PC systems. I/O may be
through DOS, Bios, direct video writes, and user-supplied drivers.
Supports I/O redirection and subdirectories.
Units--"Break large programs into logical modules and build programs
greater than 64k (large code model)." "Several powerful standard units
such as System, Dos, Crt, and Graph." Units may have init and exit code,
which is run automatically. [Don't ask for more details--that's all it
says]
Include files may be nested 8 deep. Software FP routines are faster.
Macros in Inline statements [no mention of MASM]. Variables and values may
be typecast.
All this and the MicroCalc spreadsheet, too! How CAN you go wrong?!
Reach Borland at (800) 543-7543, (408) 438-8400, or at 4585 Scotts Valley
Drive, Scotts Valley, CA 95066. Upgrade offer expires Nov. 30, 1987.
Disclaimer: I am in no way connected with Borland except as a onetime
customer.
Kenneth Herron nu113738@ndsuvm1.bitnet.UUCP (10/27/87)
I also, just received the offer from bordland for the v4.0 upgrade.
It looks like it has some impressive features. With online help, and
user interactive pull down windows, it should be easy to use. I am
an avid fan of turbo pascal. The only option I wonder about is the
"high degree of compatibility with 3.0". Just what is high compatibility.
Although, 27,000 LPM is when run on an 8 mhz AT. Still its impressive,
our mainframe here can compile pascal at about an average of 60-70000 LPM.
Also, does anyone know if bordland has a modula-2 compiler ? I asked on the
other modula-2 conf and no one has responded.
Jeff
-- A profound saying means everything or nothing depending on what
you read into it. --archer@elysium.SGI.COM (Archer Sully) (10/30/87)
In article <397NU113738@NDSUVM1>, NU113738@NDSUVM1.BITNET writes: > I also, just received the offer from bordland for the v4.0 upgrade. > It looks like it has some impressive features. With online help, and > user interactive pull down windows, it should be easy to use. I am > an avid fan of turbo pascal. The only option I wonder about is the > "high degree of compatibility with 3.0". Just what is high compatibility. > Typically, high compatibility means that it will accept the same input language. That means that Borland probably maintained a lot of Turbo's well known extensions to Pascal. Most likely they're pretty sure that most everything will compile, but they don't want to commit to it. > Also, does anyone know if bordland has a modula-2 compiler ? I asked on the > other modula-2 conf and no one has responded. Last I heard Turbo-Modula-2 hit a snag because the initial designed wasn't 'Borlandized'. Just what was wrong with it I don't know. There will probably be one eventually, but it probably will be released with warning. > > Jeff > -- A profound saying means everything or nothing depending on what > you read into it. -- archer
Isaac_K_Rabinovitch@cup.portal.com (11/01/87)
I'm about 50% convinced to spring for the Turbo 4.0 upgrade. (Not
very willingly--the $40 Borland wants for the upgrade must be close
to their wholesale price for the product itself! Essentially, I would
be buying the same product from them twice.) Some questions that might
persuade me (one way or the other):
Does the upgrade come with an improved manual? I think we can agree that
the old manual could serve as a technical writing text on what *not* to
do.
Does the upgrade fix the careless little glitches in the compiler? For
example, if you READ a number with 3.0, it must be terminated with a
blank or EOL, whereas all the textbooks tell you that a Pascal number
ends with any character that isn't part of the number. (Criswell predicts
that Borland knows about this glitch but kept it in 4.0 for the sake of
compatibility.) Anyone know about this or other glitches?
Isaac Rabinovitch
isaac.rabinovitch@cup.portal.com
sun!portal!cup.portal.com!isaac.rabinovitch
Disclaimer: Just because I think you're wrong, doesn't
mean I don't think you're a fun person!
:-)pearl@porthos.rutgers.edu (Starbuck) (07/14/88)
Howdy! By mistake, I recieved Turbo Pascal 4.0 on 3.5inch diskettes. The actual Turbo Pascal disk (not the sample program disc "Microcalsc"?)is too big to transfer to 2 5.25 diskettes, so... Could someone with Turbo on 5.25 disks, mail me the directory contents of each of the 5.25 disks so I can distribute them properly. Thanks! Steve Stephen Pearl (Starbuck) Work: (201)932-2443 Home: (201)246-3927 UUCP: rutgers!topaz.rutgers.edu!pearl ARPA: pearl@topaz.rutgers.edu US MAIL: LPO 12749 CN 5064, New Brunswick, NJ 08903 QUOTES: "What is Starbuck-ing?" -Adultress 19 "Works for me!" -Rick Hunter (The Cop, not the Robotech Defender)
mercier@rupert.iro.umontreal.ca (Denis Mercier) (08/25/88)
Can someone help with the KEEP procedure of Turbo Pascal 4.0 ? I tried to make a program to TSR. This program is an interrupt handler for MS Mouse, it run well when i try it directly but when i want it to TSR with keep an allocation memory error is signaled. And the message add that command is not found and the system halted. So i try a trivial (begin end) program to TSR and i got the same error. Did someone have experiment the same problem and got a solution ? If so i would appreciate to get your help so much. You can mail directly to (mercier@iro.umontreal.can) or reply to rn. Thanks. Denis LifeGuard Mercier.
lowey@dvinci.USask.CA (Kevin Lowey) (08/28/88)
In article <640@mannix.iros1.UUCP>, mercier@rupert.iro.umontreal.ca (Denis Mercier) writes: > Can someone help with the KEEP procedure of Turbo Pascal 4.0 ? > i try it directly but when i want it to TSR with keep an allocation > memory error is signaled. And the message add that command is not found > and the system halted. The problem is probably with your heap space. Turbo Pascal assumes you want to use ALL available memory for the program. What happens is your TSR program grabs all the available memory. When you exit the program, MS-DOS tries to load the COMMAND.COM program, but there is no room because your TSR program has grabbed all the memory, so the system is halted. The solution is to add the following line at the beginning of your TSR: {$M 16000,0,0} The first number is the maximum size for the STACK. You can probably reduce the number from the default of about 16000. The second number is the minimum size for the heap, which is 0 bytes. The third number is the maximum size for the heap. Since a Turbo Pascal TSR should not use any of the memory managment routines (NEW, GETMEM, etc.) there is no need for a heap, so this maximum value should also be 0. -- Kevin Lowey