On Sun, 13 Feb 2005 [EMAIL PROTECTED] wrote:
I was thinking that rather than linking against the recode library (and
implicitly importing all symbols within it), we could instead dlopen() it,
and use dlsym() to import only symbols we want. Looking at the recode
extension, theres only a
On Sun, 13 Feb 2005, Christian Stocker wrote:
There are new features in 5.1, which only run with 2.6 (the new error
handling system, for example, or proper namespace support for SAX).
Those are currently ifdef'd, but it definitively would make the life of
the XML maintainers a lot easier, if
Marcus Boerger wrote:
Hello Adam,
ok, you propose a function to prepare the doc comments for further
processing. While this seems a good idea at first glance it is not
that easy as you typed it. The problem is that there are different
tags some of which stop at the next tag, some are just valid
On Sun, 13 Feb 2005, Christian Stocker wrote:
Which is still less than 2.5.11, which is required for 5.0. Therefore
Debian Stable people had to face this problem already with 5.0 ;)
Fair enough. Asking people to upgrade to 2.6.x vs 2.5.11 is minor.
-adam
--
[EMAIL PROTECTED] |
Hello Marcus / Adam,
While I have nothing against some kind of comment parser in the PHP core, I
think it's something which can be done perfectly in the userland (when the
ReflectionParameter::getDocComment() is added).
Instead I would like to see the XML Canonicalization functionality from
Hello Johannes,
Saturday, February 12, 2005, 11:39:30 PM, you wrote:
[...]
While writing this mail I did some deeper look on the getDocComment stuff and
found that my it doesn't work example[2] was the only case it doesn't work
- just adding some statement behind the comment frees the
On 13.2.2005 19:08 Uhr, David Kingma | jool.nl wrote:
Hello Marcus / Adam,
While I have nothing against some kind of comment parser in the PHP core, I
think it's something which can be done perfectly in the userland (when the
ReflectionParameter::getDocComment() is added).
Instead I would like
Hi,
==
Short version:
I have concerns about the disclosure of error messages using glob() as
it reveals file names that a user should not have access to. I have
written to security@ but got no answer and the related glob()-bug
(#28932) has been marked bogus even though I pointed out that the
Is there a set of functions within an extension that is called automatically
by the ZEND engine framework to initialize and deinitailize the
extension?
In a particular PHP script, a user may call a method that sets up an
environment. I cannot always rely on the user to call the cleanup API
