"compile" vs. "tokenize" (was Re: Password Problem)

Jean-Pierre A. Radley appl at jpr.com
Tue Jun 1 13:34:10 PDT 2004


Mike Schwartz-PC Support & Services propounded (on Tue, Jun 01, 2004 at 01:42:15PM -0500):
| > | Well, to be "buzzword compliant", I would say that "filePro compiles to
| > | a bytecode for the filePro Virtual Machine".
| > |
| > | Basically, it gets compiled to machine code.  It's just that the machine
| > | that it compiles for is not the physical machine that you're running.
| > 
| > So: in the context of filePro, what does "tokenize" mean?
| > 
| > JP
| 
| 	I always thought that if ABE was *not* set to ASCII, then when you
| saved a .PRC, it "tokenized" it and saved it as a non-human readable token
| form.  So, like you, I've always been puzzled that quickstart tables were
| named .tok, when they were some other kind of compiled code.

No, when ABE != ASCII, the tables are just encrypted.

-- 
JP


More information about the Filepro-list mailing list