tcl-websh-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "pongi" <>
Subject Re: why? (Websh vs. PHP)
Date Fri, 02 Apr 2004 12:38:06 GMT
Understanding the error is not so user-friendly: if i make some errs and
try to load the page I get only a 500, and then I have to look for the
error in the apache's error_log.

I'm not a experienced programmer, so I was bored by the overwhelming
complexity I just discovered reading how to work with sessions (still
havent found if a filesession remains across pages (not just
web::commands), and how to check if a session is set)

Thank you for your advices


ps. First thing I did was this proc: 
proc print {string} {
   web::put "$string\n"

the word "web::put" is so uncomfortable ;-)

-----Original Message-----
From: Ronnie Brunner <>
To: pongi <>
Date: Fri, 2 Apr 2004 14:00:42 +0200
Subject: Re: why? (Websh vs. PHP)

> Hi
> > I'm a newbie to websh, and I'm feeling quite lost because everything
> i
> > used to get from my php scripts easily, seems very much longer and
> more
> > complex (causing difficult debug, trying to understand that damned
> error
> > log) with websh.
> You already have plenty of good reasons, why Tcl based Websh as a
> development environment for way more than just Web-Hacking from David.
> In addition: let us know of ideas to improve Websh. There is always
> room for improvement. What would make "that damned error log" easier
> to read? For an experienced Tcl hacker, Websh should be pretty
> straight forward to use (imho) but if we learn more about what's
> difficult to understand we can improve the documentation, the examples
> etc.
> Regards
> Ronnie
> ----------------------------------------------------------------------
> Ronnie Brunner                   
> Netcetera AG, 8040 Zuerich   phone +41 1 247 79 79 fax +41 1 247 70 75
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message