>>
>>OK but why do you need at runtime compilation? Or why do you store that info there while it's already in exe or typed (?).
>>Execscript() might also help but has some problems.
>
>You see, as I wrote to Hilmar, the information is not in the .EXE. The .EXE file will create the .prg file on-the-fly based on the data. Then compile it, then erase the .prg file.
Do you really nead a
compilation, i.e., are you going to run the thing, or do you just need to save information? You said "text won't do", OK, but you can somehow encode your information. Here is a simple encoding scheme: Add 15 to the ASCII value of the first byte, 43 to the second, and 5 to the third. Repeat for every group of 3 bytes. You can use a longer sequence, and different values, of course - these values are quite arbitrary.
(I have no idea how secure this system would be.)
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
