Re: And now, from the author of the DOS Disk post, a post that actually relates to this newsgroup.

[nobody@wavetech.net (Greg Buchner)]

In article <1e17yeq.16d8k6h1ff8ugwN%dempson@actrix.gen.nz>,
dempson@actrix.gen.nz (David Empson) wrote:

> Jon Bettencourt <jonINTERNETrelayCHAT@napaVALLEYnet.CLARInet> wrote:
> 
> > I tried the Beagle BASIC Compiler, but it seems to only compile COM files,
> 
> Is this 'COM' a ProDOS file type?  According to the file type notes,
> 'COM' is file type $59, and is described as a "Communications file",
> with an application-specific auxiliary type.  None of these had been
> defined as of the last publication of the file type notes.

Not an official one...it's the same hex value as integer in ProDOS,
but under the various Beagle Bros. Compiler front ends the file shows
up as COM.
 
> I've never used Beagle Basic, but it might be using this filetype for
> some kind of special binary image file which needs to be used in
> conjunctin with a front end or runtime engine.

It's not Beagle Basic, I seem to remember that being a different 
product.  Beagle Compiler consists of two parts...a seperate compiler
program that's not needed to run the programs and varios front-end
replacements for BASIC.System.  There was one for 64K, one that would
handle Aux-Slot memory for more variable space, one that used slinky
ram and one for the GS.  I started to get into that for a program I
was starting to write that I figured would have needed about 64K of
variable space.  Never did get around to getting too far on it.

The best I can remember about how it worked was than when you compiled
a program, it set up hooks to fast machine language routines in the 
front end that replaced all the BASIC stuff.

Greg B.
-- 
Note:  To e-mail me, replace nobody with gjb
I don't get junk e-mail and intend to keep it that way.
If you want to send me spam, go jump off a cliff and make
the world a nicer place.