On Fri, 13 Feb 2004, Sterling Hughes wrote:
> > And my point is that I may want to create an exception (sterling's
> > 'InternalException', for example), that I do not want you catching
> > unless you specifically check for it.
>
> Right. Exception heirarchies are nice and all, but sometimes you
>
> The reasoning is that it allows users to do a catch-all (which otherwise
> we'd add to the language syntax). It also adds cleanliness to the Exception
> hierarchy and allows PHP code to interact with PHP code which isn't written
> by the developer knowing that there's a common interface (su
>
> On Feb 13, 2004, at 11:35 AM, Adam Maccabee Trachtenberg wrote:
> >Andi's point, I believe, is that otherwise we'll need to add a
> >"finally" keyword to make sure some random extension doesn't throw
> >some random undocumented exception that you could miss. And I agree
> >with him. It just se
At 08:51 AM 2/13/2004 -0500, George Schlossnagle wrote:
On Feb 13, 2004, at 8:39 AM, Andi Gutmans wrote:
At 08:12 AM 2/13/2004 -0500, Sterling Hughes wrote:
What is the reasoning for this new change?
The reasoning is that it allows users to do a catch-all (which otherwise
we'd add to the languag
At 08:12 AM 2/13/2004 -0500, Sterling Hughes wrote:
> zeev Thu Feb 12 05:24:40 2004 EDT
>
> Modified files:
> /ZendEngine2 zend_default_classes.c zend_default_classes.h
> zend_execute.h zend_execute_API.c
> Log:
> Exceptions updates:
>
> - Enforce exc
George Schlossnagle wrote:
On Feb 13, 2004, at 11:35 AM, Adam Maccabee Trachtenberg wrote:
Andi's point, I believe, is that otherwise we'll need to add a
"finally" keyword to make sure some random extension doesn't throw
some random undocumented exception that you could miss. And I agree
with him
Hi
What are the functional or practical differences between loading a custom
extension via 'extension=' in the php.ini file and having the extension
automatically load by building php using --enable? I have an extension that
calls libraries written in C++ and I see sporadic core dumps when loa
On Feb 13, 2004, at 11:35 AM, Adam Maccabee Trachtenberg wrote:
Andi's point, I believe, is that otherwise we'll need to add a
"finally" keyword to make sure some random extension doesn't throw
some random undocumented exception that you could miss. And I agree
with him. It just seems to make every
translating Smarty! document to Korean.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
From: Andi Gutmans
> When you do something like:
> print $sxe->name->asXML();
>
> asXML() prints the XML for the whole object and not for the node.
> I think it's a bug. Can one of the SimpleXML maintainers please take a
look
> at this?
Fixed. Thanks,
Rob
--
PHP Internals - PHP Runtime Develop
On Fri, 13 Feb 2004, Martin Jansen wrote:
> Hey,
>
> error_reporting(E_ALL);
>
> echo $$foo;
> ?>
>
> results in
>
> Notice: Undefined variable: foo in /foo/bar.php on line 4
>
> Notice: Undefined variable: in /foo/bar.php on line 4
>
> Wouldn't it
Martin Jansen wrote:
Hey,
echo $$foo;
?>
results in
Notice: Undefined variable: foo in /foo/bar.php on line 4
Notice: Undefined variable: in /foo/bar.php on line 4
Wouldn't it be more appropriate if the second notice was something like
"Notice: Undefine
Hey,
results in
Notice: Undefined variable: foo in /foo/bar.php on line 4
Notice: Undefined variable: in /foo/bar.php on line 4
Wouldn't it be more appropriate if the second notice was something like
"Notice: Undefined variable: in /foo/bar.php on line 4"?
--
-
At 22:50 12/02/2004, Andrei Zmievski wrote:
On Wed, 11 Feb 2004, Zeev Suraski wrote:
> By the way - dl() is trivial to implement if we were to go down your path,
> and make dl()'s persist forever. However, that's exactly where the
problem
> is coming from - it completely doesn't fit the theme of
Hey,
When you do something like:
print $sxe->name->asXML();
asXML() prints the XML for the whole object and not for the node.
I think it's a bug. Can one of the SimpleXML maintainers please take a look
at this?
Thanks,
Andi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe
Damn it went before I finished :(
class Test
{
function __construct()
{
print simplexml_element::asXML(); // crashes as simpleXML is not expecting this is
valid.
}
}
$a = new Test();
As I was saying:
function asXML is defined as:
SXE_ME(asXML, NULL, ZEND_ACC_PUBLIC)
so it
I started running through dom and have now run into a lot of issues I need to get
resolved. Not sure if they are problems with the extension or engine bugs. Here is
what I am running into.
Can no longer call static methods:
i.e. DomDocument:loadXML() - results in Non-static method error (thi
17 matches
Mail list logo
