At 09:45 AM 11/18/99 -0500, you wrote:
When I run into a problem with my REBOL CGI scripts I just use the following
lines of code:
debugit: true
if debugit [ print [{Content-type: text/html} newline ] ]
Then if your REBOL script runs into any errors (after the lines stated
above) the errors are displayed in the Web browser.
>
>
> icimjs has the right idea...
>
> I was wanting to hear more suggestions on how people are doing testing.
> With all the discussion from new-REBOLs about CGI-GETS and CGI-POSTs.
>
> I had asked ... how do you test the stuff?
> ; -- icimjs script snip
>
> if error? try [
> all your code here
> ] [ quit ]
>
> ;-- end of script snip
>
> That works good! Thank you.
>
> As I understand it, with most CGI's in REBOL (or simple PERL scripts)
> a new instance of the program is loaded each time.
>
> (We are not talking about a REBOL modified version of Apache here.)
> Just talking about simple CGI's.
> The script should:
> 1. load REBOL
> 2. run the script
> 3. quit
>
> Another question: Is REBOL automatically supposed to quit if invoked
>with the --CGI flag.
>
> You don't want any instances of REBOL still in memory or the webserver
> will eventually run out of memory - get it?? That is why HALT is not a
good
>idea.
>
> Any other ideas for testing CGI-GETs and CGI-POSTs.
>
>
>
>From: [EMAIL PROTECTED] on 11/18/99 01:54 AM GMT
>
>
>
>Please respond to [EMAIL PROTECTED]
>
>
>
>To: [EMAIL PROTECTED]
>cc: (bcc: Doug Vos)
>Subject: [REBOL] ZOMBIES? Re:(2)
>
>
>
>
>Hi doug,
>
>you may try embedding your script in one big try block and executing quit
>if try fails. I.e.
>
>if error? try [
> all your code here
>] [ quit ]
>
>
>Also, always a good idea to test your scripts, before you use them ...
>
>Using halt won't do the trick since what halt does is:
>>> help halt
>Stops evaluation and returns to the input prompt.
>
>And the input prompt is not where you want to end up ...
>
>Elan
>
>
>
>
>
Mike Yaunish
email: [EMAIL PROTECTED]
