Re: Trace suggestion

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

Alan Oxley wrote:
> I know the "nice to have's" list is closed for v2.5,
>  but how about this for v2.6:

It's not exactly "closed", but I don't want to delay
the release too much longer.
 
> When you are in the trace(1) interactive screen, the source line numbers
>  are displayed. How about displaying the full path/filename of the file
>  being traced too? In the yellow line that prompts for a variable.

The filename is displayed in the top left corner of the screen.
It doesn't have the full path. I thought that would take up too
much space.
 
> Ideally, Id like to have tracing on in my source, and exclude tracing
>  all (trusted) includes but be able to easily override this as required.
> 
> eg: 
> a) a new trace variable "with trace_include on/off" and 
> "with trace_include_nesting_level n" 
> b) or, 'with trace_exclude="c:\euphoria\include' and I put my 
> include source in another directory
>   
> My reason for wanting this, is that its a pain to add the trace(1) 
> and trace(0) in included files, Id like to keep them untouched ,
> so that the contributor knows they are vanilla and I don't pick
> up traces while working on a different program. 
> 
> Its easier to edit ONE file only.
> Further, this will disable leftover trace on in included files.

OK, thanks. I'll add this to my list of ideas for improving
the trace facility.

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