More on fP 6.0 features

[Brian K. White]

Fairlight wrote:
> BASE64( TO|FROM , INFIELD, OUTFIELD)
>
> m->


rather:

crypt(ecoding,key,direction,source,target)

encoding is an ever growing list, initially base64 and crypt at least, mybe 
rot13(w/ rot5 numbers) just for giggles
key is the password or key, ignored/optional where meaningless such as 
base64 & rot13
direction is encode or decode, or ignored/optional where meaningless such as 
crypt & rot13
source is the input field
target is the output field

encoding, key, and direction should all accept expressions
source & target should allow specifying the same field for both

can also be used to test a public key against a private key, in which case:

key is the public key
source is the private key
target returns "1" if the keys mate

at first I though that should be done by returning an errorlevel like aa = 
crypt(...) but it's probably only meaningful a small fraction of the time so 
why make everyone burn a variable all the time for nothing?

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani