le private means only owner can
> write, readable protected means owner and descendants can write and
> readable public is just public. This would make more sense - if we decide
> readable should be a modifier, of course.
To me it seems this is going to lead to: (unwanted)
readonly publi
ecifically
> designed to parse source code files and automatically generate documentation
> skeletons from these specially formatted blocks.
I thought that {{{ and }}} were there because they are markers for vim code
folding.
--
Met vriendelijke groeten,
Tim Van Wassenhove <http://timvw.madoka.be>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
gt; have the tools to build one ourselves :(
It seems microsoft gives you these tools for free nowadays:
http://msdn.microsoft.com/visualc/vctoolkit2003/
--
Met vriendelijke groeten,
Tim Van Wassenhove <http://timvw.madoka.be>
--
PHP Internals - PHP Runtime Development Mailing List
To
you know in
>> no-time what to change.
>
> That's pretty cool. I always forget about the -l option. Thanks.
Scripts might act weird if you have spaces or other odd chars in your
directory names.
find . -name '*.php' -exec php -l {} \;
--
Met vriendelijke groeten,
Tim Van Wassenhove <http://timvw.madoka.be>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
wrapper functions, there will be a huge problem in maintaining
> it.
Although my experiences with pecl are very limited (still reading up
documentation..) i think this may be useful:
http://bugs.tutorbuddy.com/php5cpp/php5cpp/
--
Met vriendelijke groeten,
Tim Van Wassenhove <http://www.
