1. Whining time....
Rob,
A while back I asked why we couldn't trace a bound Euphoria program any more.
We had that feature in 2.4 and then it was gone in 2.5.
Let me give you a real world example of why this is still a good option. I have
a user of FROG who is running i5/OS V5R4 and is reporting a problem with the
program. My difficulty here is that V5R4 was just released a few months ago and
I don't have access to this release yet. It would be really nice to be able to
send him my bound program with the abiliy to debug on site and find out what
changed in the OS to cause the program to fail.
I'm also back to my rational for this: if I decide to send out a bound
executable with tracing on then that's my problem. Unless that is, it somehow
compromises the interpreter.
Jonas Temple
http://www.yhti.net/~jktemple
2. Re: Whining time....
Jonas Temple wrote:
> A while back I asked why we couldn't trace a bound Euphoria program any more.
> We had that feature in 2.4 and then it was gone in 2.5.
To do that in 2.4 I believe you had to bind or shroud with an option
that made your source code non-shrouded, i.e. your user would be
able to read all of your source if he wanted.
> Let me give you a real world example of why this is still a good option. I
> have a user of FROG who is running i5/OS V5R4 and is reporting a problem with
> the program. My difficulty here is that V5R4 was just released a few months
> ago and I don't have access to this release yet. It would be really nice to
> be able to send him my bound program with the abiliy to debug on site and find
> out what changed in the OS to cause the program to fail.
>
> I'm also back to my rational for this: if I decide to send out a bound
> executable
> with tracing on then that's my problem. Unless that is, it somehow
> compromises
> the interpreter.
In 2.5, backendw.exe (or backend.exe or backendu) is used to
run bound or shrouded programs. It does not contain any code for tracing.
That allows it to be quite a bit smaller. Also, your program source
code is not present in a shrouded or bound file, though it is
still possible to get a normal, full ex.err file. By using a unified
front end parser for interpreting, translating and binding, we were
able to eliminate the dual-maintenance and incompatibilities
involved with the bind-specific parser of 2.4.
I can see the value of what you are asking for.
I'll keep it in mind when I make
any major new enhancements to the binder.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
