[comp.lang.pascal] TP/windows

elmo@troi.cc.rochester.edu (Eric Cabot) (04/06/91)

Well I just received a glossy little brochure from Borland
offering me Tp/Windows. (As I'm sure many of you did).
I was wondering if anyone out there in net-land has
actually obtained this product yet.  If so I have a couple
of burning questions.

1: Memory Usage.         
   Windows will use lots of memory. Can TP/windows programs
have  super huge (read >640K) heaps so that *finally* serious
scientific applications can be written?  I mean let's face it
folks, most scientific programs are pretty modest in code size
but are always in need of lots of data space.

2:Windosobject versus turbovision
    I've come to the conclusion that turbovision is not the most
economical way to write programs..it just eats too much memory
(as has been discussed here previously).  Does the windows object
also cut so drastically into the memory partition used by
a tp program?

3:Interlanguage support.
   The brochure claims it will be easy to mix languages 
with turbo/windows.  Is this claim truely warranted?

Go ahead, fill my mailbox, make my day.

-EC

--
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Eric Cabot                              |    elmo@uhura.cc.rochester.edu
      "insert your face here"           |    elmo@uordbv.bitnet
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=

ebergman@isis.cs.du.edu (Eric Bergman-Terrell) (04/07/91)

To answer your questions about memory access in TP for Windows, see
Charles Petzold's "Programming Windows".  There's a chapter about memory
management.

Windows will let you allocate most of the free memory - but you'll still
have to fight segmented worms (I mean segmented memory).

Terrell


In other words, if you don't mind managing multiple megabytes in <= 64K
chunks you'll be ok...


*****

Question for TP-Windows programmers:  I'm a Pascal programmer but I've
been programming Windows with BC++ 2.0...  My question - in a windows
application many of your procedures require statically bound variables
because they're called by Windows (not by your program) and must retain
various things...

How is this handled in TP for Windows?  Is there a "static" storage type
or must you use GAG PUKE globals?

*****