Attached are source/test and manual patches for the addition of two
methods to the SplObjectStorage class. These methods, removeCommon and
removeUncommon, add support for the difference and intersection set
operations, respectively.
php-src-5.3-patch.diff is against php/php-src/branches/PHP_5_3
ph
Hi!
Since my first attempt to make error reporting in PHP more efficient
(see epic thread here:
http://www.pubbs.net/200908/php/49633-php-dev-patch-error-masks.html) I
thought about another approach to fixing it.
This approach eliminates the need for additional .ini setting and
shortcuts only
On Sat Dec 18 12:33 PM, Stefan Marr wrote:
> Hi Jonathan:
>
> On 18 Dec 2010, at 18:14, Jonathan Bond-Caron wrote:
>
> > Does the order of the declaration matter?
> No, the order does not matter, and that is one of the key points of
> traits compared to mixins or Python's way of multiple inherit
Hi James:
On Sat, Dec 18, 2010 at 05:08:38PM +, James Butler wrote:
> What about people on shared hosting?
One option may be to put a in an .htaccess file.
Oh, and keep in mind .
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web
Hi Jonathan:
On 18 Dec 2010, at 18:14, Jonathan Bond-Caron wrote:
> Does the order of the declaration matter?
No, the order does not matter, and that is one of the key points of traits
compared to mixins or Python's way of multiple inheritance.
So, any kind of order-dependent solution would be i
Fiddle, hadn't thought that out. Seeing as it's a non starter for shared
hosting, then yes, it should probably be left to the web server to decide.
--
James Butler
Sent from my iPhone
On 18 Dec 2010, at 17:21, "Reindl Harald" wrote:
> They can not configure php too or the webserver allows
> th
They can not configure php too or the webserver allows
this for virtuals hosts (IIS afaik does) but on
shared hosting this had to be done from the admin
I agree that php is the wrong place
If any compnent have to say "405 Method Not Allowed"
it is the webserver long before starting the interprete
On Sat Dec 18 10:29 AM, Stefan Marr wrote:
> At least I do not find an argument for either way that completely
> convinces me.
> At the moment, the main reason is that 'public' can be considered to
> be the default visibility modifier.
> Based on the semantics of 'var' and dynamic properties.
> T
What about people on shared hosting?
--
James Butler
Sent from my iPhone
On 18 Dec 2010, at 17:07, "Daniel Convissor"
wrote:
> Hi Pierre:
>
> On Thu, Dec 16, 2010 at 01:32:15PM +0100, Pierre Joye wrote:
>
>> However I would
>> prefer to bring back a proposal we had a couple of years ago, to
Hi Pierre:
On Thu, Dec 16, 2010 at 01:32:15PM +0100, Pierre Joye wrote:
> However I would
> prefer to bring back a proposal we had a couple of years ago, to
> totally disable post data.
Completely disabling POST is something that is probably best done
via web server configurations. Doing this a
Hi Larry:
On 16 Dec 2010, at 23:31, Larry Garfield wrote:
> I am fine with this approach, with 2 caveats:
>
> - If you actually do want to make two traits use the same property, it looks
> like the answer here is "Either have no property and demand the existence of
> an accessor that returns b
11 matches
Mail list logo