Lester Caine wrote:
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.
Firstly, run-time taint could be used or appropriately extended to be
used to provide such information in your bloatware environment of choice.
Secondly, anything that could within reason have the same qualities as
run-time taint would in fact have to be run-time taint by any other
name. What do you intend to do, write an AI to analyse all the code
flawlessly without running it and cover all logical paths? Nobody cares
about taint in a hello world without any conditionals or flow control or
complexity at all. Taint is useful for large amounts of code and that
would be very hard to cover with static analysis.
Taint could be very useful as an informative tool for development and
review. It doesn't have to be implemented to always run or even be
compiled into your production installs. Please do not limit it with your
terror of including useful features.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
