Richard Lynch kirjoitti:
Maybe this check should be in a phpize-generated configure script, so
that new extensions will have it built-in?
I left it out intentionally from phpize. It is just a notice but I rather not
see any bug reports about 3rd party stuff. :)
MANY bug reports and build issues, especially for newbies, are caused
by a simple typo that this would catch, if I'm understanding what it
does without actually trying it yet...
People still have options like '--enable-track-vars' in use. :)
This feature also works as a notice for removed options, such as the late
--enable-versioning removal.. ;)
And, hey, if it helps even the experienced developers do a bit of
clean-up on old build scripts, that's a Good Thing too, imho. :-)
It already helped me to find a typo in one option..
Now if we could just get configure to HALT when an option that is
enabled by default but is specified on the command line as well isn't
available, so users aren't confused by it continuing to build
something they didn't ask for in the first place... :-v
This didn't compute. Halt on option that is enabled by default but isn't
available?? huh?
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
