On 5 Mar, David N. Welton wrote:
> Wojciech Kocjan <[EMAIL PROTECTED]> writes:
>
>> Today I've been working on debugging dtcl with debugger from TclPro (I'm
>> using free TclPro 1.4).
> Cool - does it seem pretty useful?
Yes, mostly in sophisticated code or when there are many conditions...
There's little sense in debugging 'hello world', but when I use SQL with
tcl and complex queries, it helps a lot.
>> I've been testing stuff with tclsh, but this should work with dtcl as
>> well:
> Would you mind editing this information into a 'debugging.txt', that I
> will add in CVS?
Tomorrow... or today in the evening.
>> it could be done with an option in httpd.conf - it would supply
>> directory to prodebug.tcl, host and port of remote debugger.
> Hrm... I would prefer to #ifdef it.
You are so lazy ;-)
Actually I was dreaming of either option or new file type like
'application/x-httpd-tcl-debug' or something...
You might make a parameter to parser function which and use if() instead
of #ifdef :> Shouldn't be that much harder...
Then I could run 1 Apache and have a directory in which I test the pages
(running in 'debug mode' is awfully slow!) and the rest would work
normal. Or I could make AddType ... in .htaccess for testing purposes.
I suppose it would be quite practical.
>> Since I don't know much about Apache API, I'd rather not to write it
>> myself.
> Well it's just a matter of replacing the two pieces of code, correct?
> Or are you saying something else needs to be done?
It should be enough to source 1 script more in GlobalInit (which could
be done by the user) and replacing 2 pieces of code.
So please consider making another filetype.
--
Wojciech Kocjan
email [EMAIL PROTECTED]
www http://zoro2.org
tel +48-501-778778
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
