Andi Gutmans wrote:
I don't quite understand the relevance of PHPEclipse to the issue.
And I'm not sure how you judge "clogging up" PHP without seeing a patch
especially as I'm not sure how much PHP internals hacking you've done.
I'm sure many people have their own preferred tools for creating files -
all I was trying to say was that - is taint support actually needed at
run time? Something that improves the visibility of mistakes while
editing files seems to be more worthwhile - something that can also be
switched to report compliance with other things like 'strict' before you
actually RUN a script?
Building everything directly into the runtime just seems overkill and
while I would be the first person NOT to want to have to compile before
running, some tools that assist in the development process could be
useful. Eclipse provides a tidy framework to develop in and is free so
seems the logical starting point - especially since Wietse is from IBM.
--
Lester Caine - G8HFL
-----------------------------
L.S.Caine Electronic Services - http://home.lsces.co.uk
Model Engineers Digital Workshop -
http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Treasurer - Firebird Foundation Inc. - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
