httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexei Kosut <>
Subject Re: function prototypes
Date Thu, 02 Jan 1997 01:38:52 GMT
On Wed, 1 Jan 1997, Doug MacEachern wrote:


> 'not trivial' was a poor choice of words.  It won't be that bad, but
> keep in mind, you're talking to a Perl freak.  I try to only write C
> code so I don't have to write C code (e.g. mod_perl :)  Writing parsing
> code in C _really_ bugs me since it's so easy in Perl.
> It will still be a little tricky since we don't get FILE *, and we could 
> have any number of buffers come through with different parts of the content.
> e.g.
> print "Status: ";
> print 200;
> print "\n\n";
> print "Content-type: ";
> print "text/html";
> print "\n\n";
> ...

Oh. Right. Forgot about that. I was thinking about one line per print
statement, but of course this is perfectly legal as well.

> Not that anyone would write code like this, but to give you the idea, the
> script's STDOUT is hooked up to an sfio discipline, calling our write 
> function everytime print is called.  State saving could get ugly, but I'll
> read up more on sfio and see if it might have a clean way to help out.
> Any other suggestions are welcome.

Hmm. Yes, that could get ugly. I can't think of a good way around it,

Alexei Kosut <>      The Apache HTTP Server

View raw message