Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!psuvax1!rutgers!mcdchg!tellab5!toth From: toth@tellabs.com (Joseph G. Toth) Newsgroups: comp.sys.apple2 Subject: Re: two questions... Summary: P-code vs P-system/P-interpreter Message-ID: <4673@tellab5.tellabs.com> Date: 27 Nov 90 03:46:38 GMT References: <8530@darkstar.ucsc.edu> <1990Nov5.141216.28524@mintaka.lcs.mit.edu> Sender: news@Tellabs.COM Lines: 38 In article <1990Nov5.141216.28524@mintaka.lcs.mit.edu>, dcw@lcs.mit.edu (David C. Whitney) writes: > In article <1990Nov5.112859.7962@nntp-server.caltech.edu> toddpw@nntp-server.caltech.edu (Todd P. Whitesel) writes: > >unknown@ucscb.UCSC.EDU (The Unknown User) writes: > > > >>I doubt Pascal makes a "SYSTEM"-ish file though) Jeez, that seems to be > > > >It doesn't. Apple Pascal has no knowledge of Prodos. It might be possible > > EEAACK! There's good reason. Apple Pascal compiled to P-Code (which, > by the way, will run on any machine running a P-interpreter). It did > not compile to 6502 assembly. Part of the P-system is the > P-interpreter. In order to get an Apple Pascal program to run under > ProDOS, you'll need to write a P-interpreter running under ProDOS. > Oog. Too much work for any one sane mind. P-interpreters tend to be Language context/system dependent. Due to the file structure of Apple Pascal, thers is a special option for the file close operation; close ( file_id, crunch ); where the crunch option causes a file system compression. This is file system dependent, meaning that the code compiled for this option might be handled incorrectly under a ProDOS P-code interpreter, or any P-code interpreter not using the Apple Pascal file format. Has anybody investigated Manx, Apprentice C or HyperC to determine whether either of these is a P-code system?? > -- > Dave Whitney > Every now and then one makes a mistake. Mine was probably this post. Ya know, mine probably was too... ;^) Joe Toth Tellabs, Inc. Lisle, Il.