Hi Gerard & others,
Here is what I would like to do:
There is a script called 'gbrowse', which I didn't write, but which I need
to call from within my embperl application. This script works by printing to
STDOUT.
So why not just keep it in my Apache::Registry directory and call it like
an ordin
At 6:48 AM +0100 3/9/05, Gerald Richter wrote:
The segfault of the perl-status seems to be a bug in Embperl (I will check
this later on), but I don't expect that it has something to do with getting
no content.
OK, thanks.
I would try
A) use Embperl configuration directives directly (without setenv
Terrence Brannon wrote:
* Did a mailing list ever get setup for Recordset? Should we?
Some time ago people on this list (incl. Gerald, of course ;-) ) agreed
it makes no sense to create a new list, the embperl mailing list can
serve for both (and for other related Gerald's stuff like
Apache::
* My 0.25a release of Recordset contained a number of patches. One of
the most prominent was the ability to provide pure SQL to Recordset
via the !Query flag and to retrieve it via the $makesql flag. None
of this is in 0.26
All changes are logged here:
http://www2.ecos.de/~mailarc/embper
