[aleyx]

Originally Posted by erayd

Yes. JSON doesn't allow comments (which is a total pain; it's almost perfect otherwise), and INI doesn't support subsections or list of values without a named key (i.e. a numerically keyed array). YAML on the other hand supports both of those, plus it's also really nice to work with if hand-editing it.

Fair points. It's true that JSON is pretty annoying that way. About .ini, it does allow numerically keyed arrays:

Spoiler:

[section]
option[] = value1
option[] = value2

returns, depending on parse_ini_file's options, either:

array
(
    [option] => Array
    (
        [0] => value1
        [1] => value2
    )
)

or:

array
(
    [section] => Array
    (
        [option] => Array
        (
            [0] => value1
            [1] => value2
        )
    )
)

but I have no idea if it works in more that one dimension.

Well, YAML works, and that all that matters.

Originally Posted by erayd

My understanding is that $argc and $argv are always available when using the CLI SAPI, regardless of the register_argc_argv setting. When not using CLI, we don't care about them anyway... although it would probably be a good idea to stick a php_sapi_name() call in there somewhere to figure out what kind of startup handling is required.

Indeed; if we implement flagCLI and flagWEB classes, we'll have to abstract much of that part anyway. But that's not for a little while yet ^_^

Originally Posted by erayd

I *really* don't like that idea. While 5.3 would be very, very nice to have, it's not deployed anywhere near widely enough to count on. I'd rather not make life difficult for people trying to set this up, and a large number of distros don't even ship 5.3 yet (or at least not in an easily-obtainable way).

If we are going to go down that route though, I'd rather go the whole hog and jump to PHP 6 - but I still think that requiring anything higher than 5.2 is a bad idea.

Fair enough; it's true that PHP5.3 is only mostly available in this year's releases. I still think that FLAG's user base would probably keep current though; and those that don't probably just use the online version anyway. It would be interesting to have a poll about this here ("What's your PHP version?"), if only to know exactly our minimal version target. It'd be too bad if we deny ourselves the niceties of PHP5.3 (namespaces and get_called_class() saved my sanity) for just a couple of <=5.2 installs.

But in the end, you're the boss.

N.