httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: [PATCH] Config File Line Continuation (take 3)
Date Mon, 02 Mar 1998 22:30:57 GMT


On Mon, 2 Mar 1998, Ralf S. Engelschall wrote:

>       `[!BACKSLASH] BACKSLASH [CR] LF'
>   occurs. In other words: The line is continued only when a backslash is seens
>   _directly_ before the newline and _only if_ it is not explicitly escaped by
>   another preceeding backslash.

But this still doesn't fix the RAW_ARGS problem.  Here let me find a
RAW_ARGS directive... require, it's RAW_ARGS.  Consider

require user abc\

would suddenly cause continuation, and if you say: 

require user abc\\

then you're requiring "abc\\" not "abc\". 

RAW_ARGS is incompatible with any sort of pre-processing of the input
line.  Including end-of-line comments, and line-continuation.  (corollary,
RAW_ARGS is lame.)  Most of the uses of RAW_ARGS are to handle a variable
length list of arguments... that's why I suggested it be completely
replaced by something like VAR_ARGS which calls a function with prototype:

    const char *foo(cmd_parms *cmd, void *config, array_header *argv)

array_header is constructed by iterating over the arguments with
getword_conf().  This would make things a little more consistent.

Dean



Mime
View raw message