Re: Rob: ex.err for shrouded and bound files

new topic     » goto parent     » topic index » view thread      » older message » newer message

Pete Lomax wrote:
> I'm sure you already know the ex.err output of a bound or shrouded
> file can be hard to follow, eg:
> 
>>H:\pptestexe\pptest.exe:22690 in procedure BXe()
>>... called from H:\pptestexe\pptest.exe:7681 in procedure Zv()
> 
> Would it be possible for bind and shroud to be given not only the
> original source files but also an ex.err file, and un-shroud it,
> returning the original routine, variable names and line numbers?
> 
> Either that, and probably much easier, allow a shroud -text option
> which renames as usual, but outputs a plain text file which can be
> traced. Or maybe even easier still, a -listall option which produces a
> huge deleted.txt telling me everything that has been renamed.
> 
> Any one of those three options would help me quite a bit.

Thanks. I'll consider those ideas for the next release.

If it's important to get an understandable ex.err,
you might consider the -clear option to bind/shroud,
assuming of course that protecting your source
is not a big issue.

Regards,
    Rob Craig
    Rapid Deployment Software
    http://www.RapidEuphoria.com

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu