Shire,
Xlog looks really useful. Does it also help with exception thrown
without a stack trace?
Thanks,
John.
-Original Message-
From: shire [mailto:sh...@tekrat.com]
Sent: 19 January 2009 01:45
To: PHP Internals List
Subject: [PHP-DEV] PATCH: zend_mm_heap_overflow()
I'm releasing
How about a strict mode added to the list of the current json_encode()
options?
That way current code will continue to work and anyone reading the docs
will know the default behaviour isn't strictly correct.
John.
John Carter
Development Manager
NAC Governance Server
Cisco
johnc...@cisco.com
Good idea. Would also be nice if added constants for the existing 0, 1
and 3 options.
John.
John Carter
Development Manager
NAC Governance Server
Cisco
[EMAIL PROTECTED]
+44 161 249 5825
-Original Message-
From: Stanislav Malyshev [mailto:[EMAIL PROTECTED]
Sent: 12 November 2008
We use syslog a lot. I've always found define_syslog_variables to be
pointless and frankly a little bizarre.
+1 on this.
John.
-Original Message-
From: Lukas Kahwe Smith [mailto:[EMAIL PROTECTED]
Sent: 14 October 2008 08:42
To: Kalle Sommer Nielsen
Cc: PHP Development
Subject: Re:
John Carter
Cisco - PolicyApp
[EMAIL PROTECTED]
: why can't interfaces have properties?
John.
From: Nathan Nobbe [mailto:[EMAIL PROTECTED]
Sent: 29 April 2008 16:17
To: John Carter -X (johncart - PolicyApp Ltd at Cisco)
Cc: internals@lists.php.net
Subject: Re: Re: [PHP-DEV] Class Properties in Interfaces
Marcus,
I understand why Interfaces can't have bodies, but could you explain why
Interfaces can't have properties?
Thanks,
John.
-Original Message-
From: Marcus Boerger [mailto:[EMAIL PROTECTED]
Sent: 29 April 2008 10:46
To: Jeremy Privett
Cc: PHP Developers Mailing List
Subject: Re:
]
Sent: 29 April 2008 11:17
To: John Carter -X (johncart - PolicyApp Ltd at Cisco)
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Class Properties in Interfaces?
I would start by saying it's bad design. you should use getters and
setters which you can define in you interface
--
/James
On Tue
: [PHP-DEV] Class Properties in Interfaces?
John Carter -X (johncart - PolicyApp Ltd at Cisco) schrieb:
could you explain why Interfaces can't have properties
Because interfaces are implemented which makes no sense for
attributes.
--
Sebastian Bergmann
http://sebastian-bergmann.de/
GnuPG Key
Nobbe [mailto:[EMAIL PROTECTED]
Sent: 29 April 2008 16:17
To: John Carter -X (johncart - PolicyApp Ltd at Cisco)
Cc: internals@lists.php.net
Subject: Re: Re: [PHP-DEV] Class Properties in Interfaces?
On Tue, Apr 29, 2008 at 6:28 AM, John Carter -X (johncart - PolicyApp
Ltd at Cisco) [EMAIL PROTECTED
(johncart - PolicyApp Ltd at Cisco)
Cc: internals@lists.php.net
Subject: Re: Re: [PHP-DEV] Class Properties in Interfaces?
On Tue, Apr 29, 2008 at 9:51 AM, John Carter -X (johncart - PolicyApp
Ltd at Cisco) [EMAIL PROTECTED] wrote:
The article explicitly mentions OOP interfaces in a few
I think there's been two responses to this query:
1. We can't have properties in interfaces because interfaces don't have
properties. I would say this is tautological and doesn't add anything.
2. Why would you need to? Getters and setters work.
So I suppose to answer my question for myself,
Stanislav,
I like the look of the API. The naming convention appears logical, on
the question of internal class names existing in userland I'm sure
people will refer to the discussions around DateTime.
Many extensions appear to offer procedural style equivalents to the OOP
API, personally I
13 matches
Mail list logo
