Re: New to the NET with Euphoria from a dialup on a 233mhz laptop
- Posted by Robert Craig <rds at RapidEuphoria.com> Apr 06, 2002
- 403 views
There seems to be a vague notion out there that to use Euphoria for CGI you must get a Web host to agree to install Euphoria on their system, or you must get their permission before you can use it. In my case, RapidEuphoria.com is hosted on some Web host's FreeBSD machine. It's not my machine. I have set up various Euphoria programs for CGI and for other things. I did not ask my Web host to install anything, nor did I ask their permission to run Euphoria. For CGI, I can run interpreted Euphoria programs using: #!./exu on the top line of my program. I can run bound Euphoria programs, and I can run translated-to-C and compiled Euphoria programs. All I do for CGI is put the Euphoria program into my cgi-bin directory, and set the permissions correctly. It's also convenient to have exu in there. If a Web host will let you run a C program, then they shouldn't care if you run a Euphoria program. After all, the Euphoria interpreter *is* a C program. Your code is just data for the interpreter. I've now written Perl programs, C programs and Euphoria programs for CGI. There's no comparison in terms of ease of development. With C my Web host doesn't allow any core files to be dumped, so there are 0 diagnostics when the C CGI program fails. The same is true with Perl. With Euphoria, I get a full ex.err file left in cgi-bin, and it's usually very easy to see what went wrong and to correct it. I can also turn on profiling and look at the ex.pro file. I also have a cron job that runs every hour and it's written in Euphoria. If something goes wrong, it leaves an ex.err file, and I get the Euphoria error diagnostics that normally would appear on the screen, e-mailed to me by the system. When it was written in C, I'd get "core dump" e-mailed to me, and then there was no core file to be found. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com