Re: Euphoria compiler-runtime-shrouding-binding
>Just keep a copy of your source code and take that with you instead. If
>you're paranoid about losing the original source and not being able to
>fix a customer's problems then just encrypt your source with a simple
>algorithm (how about ceaser's cypher, who'd guess that?) and distribute
>it with your executable. Put a note in the documentation that that file
>is for future maintenance and delete at own risk.
Well, the idea is that this "feature" wouldn't slow down Euphoria
interpreter and perhaps increase in 2 or 3 Kb ex.exe size... so why don't do
it? The only time you miss some "special feature" of a product is when you
URGENTLY need it... and who knows when that will happen (hope it never
happens).
>Keep it simple, we're talking about a customer here, not the KGB.
Da ;)
>By the way, great language, no I don't have the full version, I'm
>not in the programming business.
Me neither, but I enjoy programming and from time to time some friend asks
me to code something...
>Personally I think Euphoria is perfect the way it is, but that's
>coming from a guy who programs assembler on a 486 using just 8086
>opcodes and only 64K of memory. What can I say, I like simplicity.
Take note that if you want to implement some machine code routines in
Euphoria you must use 32 bit instructions, and be careful with JMP's... you
must count you're working witth 32 bits registers.
|
Not Categorized, Please Help
|
|
