---------------

FIDO MESSAGE AREA==> TOPIC: 107 PASCAL        Ref: F5G00304 Date: 04/18/98
From: KIM FORWOOD                                           Time: 04:58pm
\/To: JOEJARED@WEBWORLDINC.COM                            (Read 2 times)
Subj: Re: In case anyone is interes

joejared@webworldinc.com wrote: 
 > {$DEFINE DEBUG}
 >
 > {$IFDEF DEBUG}
 jo> why not use {$ifopt d+}
That would be okay if I only wanted to toggle one compiler directive,
but normally I use the DEBUG conditional for more than just that. I
usually add debugging code somewhere in the source and wrap it with a
{$IFDEF DEBUG} ... {$ENDIF} so that it'll automatically be compiled in
if I'm debugging. Using a conditional this way also allows me to more
easily isolate the inclusion of debugging code to selected units by
doing a search/replace of DEBUG to something like DEBUG_XYZ, so only
the DEBUG_XYZ conditional will be toggled on, rather than every unit
that uses the DEBUG conditional.
  Kim Forwood
---------------------------------------
 Internet: kim.forwood@elab.canbbs.net
  FidoNet: Kim Forwood, 1:153/831
---------------------------------------
--- Blue Wave/DOS v?.??
 * Origin: The Eclectic Lab (1:153/831)
---------------

FIDO MESSAGE AREA==> TOPIC: 107 PASCAL        Ref: F5G00305 Date: 04/18/98
From: KIM FORWOOD                                           Time: 05:13pm
\/To: CORBIN LEMIEUX                                      (Read 2 times)
Subj: Re: OO memory usage?

Corbin Lemieux wrote: 
 KF> I found something that will do it by way of either processes or
 KF> drivers. Something written by a guy named Dieter Pawelczak from
 KF> Germany. Looks quite interesting and well developed.
 CL> Is that his parallel processing unit?
Yes... And a separate driver unit in another earlier package.
 CL> What version do you have and where did you get it from.
 CL> I have an version that is a couple years old...hopefully the one you
 CL> have is newer.
I have v3.00
  Kim Forwood
---------------------------------------
 Internet: kim.forwood@elab.canbbs.net
  FidoNet: Kim Forwood, 1:153/831
---------------------------------------
--- Blue Wave/DOS v?.??
 * Origin: The Eclectic Lab (1:153/831)
---------------

FIDO MESSAGE AREA==> TOPIC: 107 PASCAL        Ref: F5G00306 Date: 04/18/98
From: KIM FORWOOD                                           Time: 05:15pm
\/To: PAUL WALKER                                         (Read 2 times)
Subj: Re: You grasser!

Paul Walker wrote: 
 PW> Kim Forwood to mark lewis, 14 Apr 98 06:04.
 
 KF> older machines where XMS may not be, thus since I use XMS it will not
 KF> be used by my programs on those older machines, but EMS could have
 KF> been had I chosen it instead. Does that sound about right?
 PW> As far as I can see, yes. The best answer I can think of is to "wrap"
 PW> memory  allocation up into a routine that will allocate XMS, EMS or
 PW> conventional  memory as available, without the caller having to worry.
I have my data storage unit so it can use XMS or conventional, and I still
have to add disk storage as a final fallback option. EMS and it's 64k page
frame limitations makes me hesitant with all the work that will be required
to manage linked buffers.
  Kim Forwood
---------------------------------------
 Internet: kim.forwood@elab.canbbs.net
  FidoNet: Kim Forwood, 1:153/831
---------------------------------------
--- Blue Wave/DOS v?.??
 * Origin: The Eclectic Lab (1:153/831)
---------------

FIDO MESSAGE AREA==> TOPIC: 107 PASCAL        Ref: F5G00307 Date: 04/16/98
From: ONNO GEENEN                                           Time: 10:09pm
\/To: PAUL WALKER                                         (Read 2 times)
Subj: turbo pascal 7.0

Hello Paul,
 > Free Pascal is okay (at least the version I've just downloaded
 > actually works!), but creates fscking massive EXE files -
 > 50Kb for hello world?!
:-)
That's a 32-bits 'Hello World' you created, the 50k also contains the 
dos-extender.
Onno
--- GEcho 1.00
 * Origin: FBBS running Fornax.  [VFC/V34, 24x7] (2:284/614.1)