I'd like to make a suggestion.  In addition to compressed/normal output, how about an option to define pseudo constants __file__ and __line__ for each line outputted.  Then the error message could be more informative during development, and turning off debugging would return to full speed.

Erick

Erick,

<< I'd like to make a suggestion.  In addition to compressed/normal output, how about an option to define pseudo constants __file__ and __line__ for each line outputted.  Then the error message could be more informative during development, and turning off debugging would return to full speed. >>

I'm not quite sure what you're asking for.

Most browsers will actually show a line # for an unhandled exception in your EWB application.  Is that what you're looking for ?

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

Erick,

<< I'd like to make a suggestion.  In addition to compressed/normal output, how about an option to define pseudo constants __file__ and __line__ for each line outputted.  Then the error message could be more informative during development, and turning off debugging would return to full speed. >>

I<'m not quite sure what you're asking for.

I'm suggesting embedding the Pascal line numbers during debug mode, so we can print the source line number in the error message.  It would speed up debugging immensely.

Tim Young
Elevate Software
www.elevatesoft.com

Erick,

<< I'm suggesting embedding the Pascal line numbers during debug mode, so we can print the source line number in the error message.  It would speed up debugging immensely. >>

I think I know what you're asking for, but just to confirm: you're saying that you want the equivalent of a source map that shows the *EWB* source line number instead of the *JS* line number during an exception ?  If so, then that will be something that will be built-in to the IDE once we swap out IE for Chrome.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

Erick,

<< I'm suggesting embedding the Pascal line numbers during debug mode, so we can print the source line number in the error message.  It would speed up debugging immensely. >>

<I think I know what you're asking for, but just to confirm: you're saying that you want the equivalent of a source map that shows the *EWB* source line number instead of the *JS* line number during an exception ?  If so, then that will be something that will be built-in to the IDE once we swap out IE for Chrome.

Wonderful, I couldn't ask for more.
Erick