Re: [gforth] Hello Everybody

[Dennis Ruffer]

Jason,

If gforth detects the error, and it is running as a script (not just gforth on 
command line), then it exits gracefully, after outputting what is, hopefully, 
useful debugging information.

Of course, you probably can guess that an endless begin...again loop is not 
actually an error. ;)

DaR

> -----Original Message-----
> From: address@hidden [mailto:gforth-
> address@hidden On Behalf Of Jason Damisch
> Sent: Saturday, July 09, 2011 1:15 PM
> To: address@hidden
> Subject: Re: [gforth] Hello Everybody
> 
> I was contacted by somebody at my hosting company, and this gentleman
> was much more helpful.  That was after I put in a complaint to Customer
> Care.
> 
> 
> He said that I needed something called VPS, virtual private server.  Their
> cheapest option is called Zen Cloud.
> 
> from their web site
> 
> "The Xen Cloud Platforms are completely independent from the hardware
> node, and
> each other. This means that you are able to run updates  independently of
> the
> hardware node. This also means that one customer  can’t crash a service or
> the
> server."
> 
> Which brings me to my next question.  What happens when I crash gforth?
> Ofcourse I would not do something intentionally wrong such as...
> 
> 0 0 !
> 
> I suppose that I could intentionally crash gforth once I get it going to see
> what happens?
> 
> 
> : test
>    begin   again
>    ;
> 
> test
> 
> 
> 
> > I contacted my hosting company, and they have not been helpful. They
> told me
> >that I do not have permission to run an executable on shared hosting.   I
> tried
> >to copy gforth to the /usr/bin/ directory using  PSCP but was denied
> permission.