Re: [PHP-DEV] [RFC] Disallow multiple default blocks in a single switch statement

in a minor release because the incomplete spec says so is kind of odd. A BC break is a BC break, which doesn't belong in a minor revision. Regards, James On Wed, Aug 13, 2014 at 3:47 AM, Ferenc Kovacs wrote: > On Wed, Aug 6, 2014 at 6:38 AM, Sara Golemon wrote: > > &g

Re: [PHP-DEV] [RFC] Disallow multiple default blocks in a single switch statement

Even if it is fall through that is causing the behavior it still is a syntax that no longer will be considered valid in a minor release - and seemingly in a point release as well if everyone had their way here. [: Not that I consider code likehttp://3v4l.org/ mtG4K

[PHP-DEV] Backwards compatibility with set_exception_handler callback and type hints

So testing out PHP 7 I triggered an \EngineException() in Drupal 8. For various reasons that don't really matter here Drupal uses set_exception_handler() to provide its own exception handler. What is important is that the methods used by that handler type hint \Exception for their arguments. The im

Re: [PHP-DEV] Backwards compatibility with set_exception_handler callback and type hints

ugh becase, we have a library(and by library I mean class) for parsing information out of exceptions. So we would have to do quite a bit more hackery then that to to keep type hinting. On Tue, Mar 31, 2015 at 8:59 PM, Dan Ackroyd wrote: > Hi James, > > On 31 March 2015 at 21:51, Jam

[PHP-DEV] Assert breaking access on objects in PHP 7

Not even sure really how to describe this but recently adding some assertions to code in Drupal caused some really weird failures. Here's a test case that sort of shows how it works. http://3v4l.org/7cQNm

[PHP-DEV] Need help finding segfault in php 7

So I've been trying for a couple days to narrow down this bug: https://bugs.php.net/bug.php?id=70242 I can consistently recreate it with a complex test, but I have thus far not been able to find a pattern that helps me narrow down to a test script. I thought maybe I could reach out and see if I co

Re: [PHP-DEV] Need help finding segfault in php 7

Man I'm glad you figured that out because even with the test case I can't figure out what's going on :) On Fri, Aug 14, 2015 at 12:15 PM, Xinchen Hui wrote: > Hey: > > > On Thu, Aug 13, 2015 at 8:36 PM, James Gilliland > wrote: > > So I've been trying

[PHP-DEV] Appropriate list for questions about extensions?

Hello all, I am new to this list and I am wondering if this is the appropriate place to ask a question about the internals for an extension, or is there a more appropriate list for that purpose? My issue is fairly technical and involved with the deep guts of Zend so I suspect this may be the r

[PHP-DEV] Issue with op_array moving

Hi all, I am writing an extension that does performance monitoring. I guess somewhat like xdebug but a bit different. The user can specify the functions / methods they care about and I will time the execution of those things. I do this by hooking zend_execute. My hook is: void rrdmon_execute

[PHP-DEV] main/output.c problem

The new output buffering mechanism has a compatibility function for people / extensions that use the "old way". There is a compatibility function php_output_handler_compat_func(). It is not quite as compatible as it should be, and any code that depends on it will break. Using the "old way" if t

Re: [PHP-DEV] PHP 5.0.4 PEAR issue

s add and cvs commit once done. I then tag with the version number, roll a release package and install it on a pre production machine. Once the package is tested on a pre production machine I know that it will be ok in userspace -- if not I source the problem and roll a pre producton package again.

[PHP-DEV] Possible error with DOMNode::replaceChild() in 5.0.4

5c0cc, this_ptr=0x835c10c, return_value_used=0) at /home/james/php-5.0.4/ext/dom/node.c:1150 1150prevsib->next = newchild; The problem seems to be related to the fix for bug #32011 (Fixed bug #32011 (Fragments which replaced Nodes are not globaly useabl

RE: [PHP-DEV] PHP 5.1

> for (...; ...; ...) { > for (...; ...; ...) { > if (...) { > ... code ... > continue 2; > } else { > ... code ... > break; > } > } > } [Further snipped to highlight important bits.] Wouldn't named b

[PHP-DEV] class_exists and __autoload

em to pass TRUE as the second parameter, but leave the default be false. Or at the very least let autoload return false, so that the rest of the script can do it's thing... or maybe allow for a php.ini option to set the default behavior to false (though this option can make some scripts

[PHP-DEV] memory corruption with 5.1?

do I run into the problem. I'm at a loss as to how to further troubleshoot this. And as the script isn't causing a segfault, I don't really know what other information to provide, or where to look. Any pointers or help with this would be much appreciated. -james -- PHP Intern

Re: [PHP-DEV] memory corruption with 5.1?

a5c822.txt/withoutmm.txt With zend mm -- https://www.die.net/tmp/00e9a7d1e7a5d0fc.txt/withmm.txt -james Rasmus Lerdorf wrote: James Crumpton wrote: I've run into a problem, when trying out 5.1.0b1, b2, and php5-200507060230, with a

Re: [PHP-DEV] memory corruption with 5.1?

The output from valgrind that I posted was from 5.1.0b2. Before posting to internals I tried php5-200507060230 from snaps.php.net with no luck... I haven't tried running that through valgrind, however, but I suspect it would produce the same output. -james Antony Dovgal wrote: On Th

Re: [PHP-DEV] memory corruption with 5.1?

ignal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 4947)] 0x4045d4f5 in _efree (ptr=0x838d02c) at /home/james/php-5.1.0b2/Zend/zend_alloc.c:302 302 REMOVE_POINTER_FROM_LIST(p); (gdb) bt #0 0x4045d4f5 in _efree (ptr=0x838d02c) at /home/james/php-5.1.0b2/Zend/zend_al

Re: [PHP-DEV] Property Overloading RFC

My concern with the self::isVirtual() syntax would be... class Base { function __get($name) { if (!self::isVirtual($name)) throw; } } class Foo { abstract public $bar = 1; } $f = new Foo; echo $f->bar; ... Are these 'virtual' members going to work like static me

Re: [PHP-DEV] [PATCH] Namespace Patch, Beta 1

Maybe I'm alone on this, but all my class files are named as Classname.class.php... (hint, hint) :) ... On second thought, maybe it would be interesting/useful to have some mechanism to allow a formatted string like "%s.foo.php" or "foo.%s.php" to be used by spl's autoload? Not really sure ho

Re: [PHP-DEV] FORM accept-charset was: PHP Unicode support design document

re's actually a completely reliable way of working. ASCII is the only thing guaranteed to work according to the specs (at least, that's my reading), but some browsers will do strange things. If you really want to transport general character data from HTML FORMs, use multipart/form-data.

Re: [PHP-DEV] PHP 6.0 Wishlist

default: echo "it was no number :-(\n"; break; } *shrug* -james Ron Korving wrote: > I have another idea I came up with today: regular expression switches, but > it would be difficult without adding to the syntax. > > switch ($st

Re: [PHP-DEV] Issues with PHP 5 on Windows 98

HI Andreas Why are you using Windows 98.. it's full of holes and has been superseded? I know their has been some discussion on internals about dropping win98 support - see "Win9x support in PHP" for more. Cheers James On 9/27/05, Andreas Ahlenstorf <[EMAIL PROTECTED]> wro

Re: [PHP-DEV] Re: CLI in PHP6

there are plenty of processes that run happily for months on W2K Server. James -- james aylett, chief technical architect tangozebra 020 7535 9814 This e-mail has been scanned for all viruses by Star. The service is

Re: [PHP-DEV] what happened to that new isset() like language

o this. What's the word on this? Some of the names given were: issetor ifsetor ifset ifnull coalesce I'm actually kind of partial to: $a = $foo || $bar; $a = $foo || $bar || $xyz || $etc; Or better yet (or maybe in addition too): $a['foo'] ||= 'bar'; // if set do n

Re: [PHP-DEV] what happened to that new isset() like language

ficult to remember for either their name (issetor? ifsetor? ifset?) or the order of arguments thereof (ie. array and string handling functions). Sebastian wrote: Wow, it'll be just like perl! this is so great. On 10/28/05, James Crumpton <[EMAIL PROTECTED]> wrote: Andi Gutmans w

Re: [PHP-DEV] what happened to that new isset() like language

if ($a === true) { } But anyone doing that should probably have their head examined. Anyway... Regardless of what can be said about changing the behavior of '||', the same isn't true for '||=', as it has no precedence in PHP. -james Greg Beaver wrote: James Crumpto

Re: [PHP-DEV] what happened to that new isset() like language

if ($a === true) { } But anyone doing that should probably have their head examined. Anyway... Regardless of what can be said about changing the behavior of '||', the same isn't true for '||=', as it has no precedence in PHP. -james Greg Beaver wrote: James Crumpton wro

[PHP-DEV] CVS Account Request: james

Assisting with maintenance of the documentation starting with user notes, and eventually editing of the manual itself. I have subscribed to the relevant mailing lists & introduced myself, and Philip Olson has confirmed I should apply for CVS access here. -- PHP Internals - PHP Runtime Developm

[PHP-DEV] PHP_5_3 GOTO?

ts. I thought it was version PHP 6 that was adding the goto operator. Does anyone know the state of things for the goto keyword and PHP 5.3? Thanks /James -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] iconv_mime_encode(), broken Q scheme

iconv_mime_encode seems a bit broken for Q scheme, see http://bugs.php.net/bug.php?id=43314 Could some one please apply the patch to CVS trunk. I've tested and it seems to work. Thanks -- /James

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, Apr 29, 2008 at 11:07 AM, John Carter -X (johncart - PolicyApp Ltd at Cisco) <[EMAIL PROTECTED]> wrote: > Marcus, > > I understand why Interfac

[PHP-DEV] Name resolution rules

e that now a name *DOES* clash, but this time with out so much as an error! I preferred it to highlight the fact that I had a class with the same name. Any thoughts? /James

Re: [PHP-DEV] Alternative to multiple namespaces per file

what I find really annoying about all this namespace stuff, is how would that be any different from class Fully_Qualified_Class_Name_Declaration { } /James On Sat, May 31, 2008 at 1:10 PM, Stan Vassilev | FM <[EMAIL PROTECTED]> wrote: > > Hi, > > I suppose this has been di

Re: [PHP-DEV] Alternative to multiple namespaces per file

implents MyInterface { } I have reservations in using :: as a resolution operator which can easily clash with normal class space usage. Is it too late to have these discussions?? It seems I missed the big namespace discussions on the mailing list and things have already gone ahead. /James On Sat

Re: [PHP-DEV] Alternative to multiple namespaces per file

On Sat, May 31, 2008 at 6:01 PM, Larry Garfield <[EMAIL PROTECTED]> wrote: > On Saturday 31 May 2008, James Dempster wrote: > > I would agree with you, I think namespaces should wait for a later > version. > > Maybe 6 or even later. I believe there are many problems that

Re: [PHP-DEV] simple solution to another namespace conundrum?

I find it interesting that we could quite possibly get just as many clashes with namespaced code. Of course it comes down to how well the developer implements there code. It's almost like namespace is just a method of aliasing long class names. On Tue, Jun 24, 2008 at 4:38 PM, Lukas Kahwe Smith <[

Re: [PHP-DEV] simple solution to another namespace conundrum?

I would agree, they seem to cause more problems and pollution than it would solve. I like the idea behind namespaces but what I've seen of the current implementations I would rather do without. Unfortunately I don't have any ideas or solutions to the problems. /James Dempster On T

Re: [PHP-DEV] [RFC] E_USER_DEPRECATED

+1 from me in PHP 5.3 deprecation notices have been split of from E_STRICT into E_DEPRECATED On Sun, Jul 20, 2008 at 6:45 AM, Nathan Nobbe <[EMAIL PROTECTED]> wrote: > On Sat, Jul 19, 2008 at 4:55 AM, Lars Strojny <[EMAIL PROTECTED]> wrote: > >> Hi everbody, >> >> regarding my mail from yesterda

Re: [PHP-DEV] namespaces and alpha3

On Fri, Oct 10, 2008 at 5:56 PM, Geoffrey Sneddon <[EMAIL PROTECTED] > wrote: > > On 10 Oct 2008, at 06:03, Lukas Kahwe Smith wrote: > > 1) rip them out >> > > I'm +1 on this. We simply don't have consensus, and I don't see anyway we > can have consensus by the time 5.3 has to be frozen. Once nam

Re: [PHP-DEV] namespaces and alpha3

On Tue, Oct 14, 2008 at 1:34 PM, Jean-philippe Serafin < [EMAIL PROTECTED]> wrote: > Many people have starting working on top level application using > namespaces, so there will a very bad buzz over the php community if > namespaces are ripped out... There code should work fine in PHP 6 without

Re: [PHP-DEV] my last attempt at sanity with namespaces

If I understand correctly I vote. +1 for Issue 1 option 1 +1 for Issue 2 On Wed, Oct 15, 2008 at 9:35 PM, Greg Beaver <[EMAIL PROTECTED]> wrote: > Hi, > > http://wiki.php.net/rfc/namespaceissues > > Read it and discuss. Let's be clear people: the technical problems in > namespaces are limited a

[PHP-DEV] where to request small enhancements?

, users should have the ability to clear the 'last error' at their will. ANYWAY where would I post something like this? I don't want to put up my code because a.)I can't find it anymore and b.)it'd probably be embarrassing to show my crap C! -James -- PHP Internals -

Re: [PHP-DEV] Anonymous Function

PHP 5.3 has anonymous functions. James Logsdon On Fri, Nov 21, 2008 at 2:27 PM, Kenan R Sulayman <[EMAIL PROTECTED]>wrote: > Hey out there! > I've got a maybe simple question: > Where the point of not implementing anonymous functions in php alike > javascript? > &g

Re: [PHP-DEV] Re: [PHP-CVS] cvs: php-src(PHP_5_3) /ext/stan ... Deprecate ticks, pcntl_signal affected?

;s exactly why I don't see how we can deprecate ticks without > introducing a replacement. > > -- > Wbr, Antony Dovgal > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > What was the outcome of this? I've just started using declare ticks for signal handling and now see that in 5.3 it will depreciated and in 6 removed! :-/ Thanks, /James

Re: [PHP-DEV] Re: Is it true that short_open_tag is deprecated in PHP 6?

I think that's what he meant by "escape it". I haven't used short_open_tags myself much, but as I've been exploring templating options I like it for outputting variables. James Logsdon On Mon, Apr 13, 2009 at 2:24 PM, Kalle Sommer Nielsen wrote: > 2009/

[PHP-DEV] PHP Array Literals

Hi, I've written a short paper on some changes that I'd like to see made for array literals in PHP. If you could please take a look and give your thoughts, I'd greatly appreciate it. http://www.matttoddphoto.com/papers/php_array_literals.html Thanks, M.T. -- PHP Internals - PHP Runtime Developm

Re: [PHP-DEV] PHP Array Literals

No, it's definitely not that hard to write, but I have seeing 'array()' everywhere when I know damn well that it's an array. Concerning the 'pass by reference' problems, I'm going to assume that that's happening when you're working with some of the functions already in PHP or someone else's code,

Re: [PHP-DEV] PHP Array Literals

Then why don't we have these: $i = integer(5); $f = float(4.5); $s = string("foo"); And what about classes? It's slightly different, what with it being a definition rather than a specific literal value, but it produces a definition, pseudo value if you will, so why not have: class("MyClass", arr

Re: [PHP-DEV] PHP Array Literals

Or could learn that [] creates arrays the same way that it is used to access and assign pieces of arrays. M.T. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] PHP Array Literals

So, all I heard as reasons not to introduce the '[]' syntax for creating arrays is because "'array()' is perfectly fine" and that it wouldn't make sense to have two syntaxes (compared to other legacy stuff in PHP). And certainly nobody has an objection to the fact that developers have to learn that

Re: [PHP-DEV] PHP Array Literals

[Reply below] On 2/2/06, Christian Schneider <[EMAIL PROTECTED]> wrote: > While I would kinda like array literals too (and even had a patch for it > some time ago, don't remember if it was without problems though) the > core developers think that > a) one working solution is enough > b) array() is

[PHP-DEV] "Pushing PHP Into The Web 2.0 Generation"

I've written a short paper on the future of PHP and I'd appreciate it if you folks would take a look at it and exchange your thoughts with me. http://www.maraby.com/papers/pushing_php_into_the_web_20_generation Don't be too skeptical. ;) Cheers! M.T. -- PHP Internals - PHP Runtime Development

[PHP-DEV] Design By Contract

I've been reading and I discovered a concept called Design By Contract. I've not seen any particular libraries to aid in this particular development design process, but I was wondering if you folks had, or if there were plans to consider providing for this functionality within PHP. (A longshot, I k

Re: [PHP-DEV] Re: [EMAIL PROTECTED] RE: [PHP-DEV] new apache fastcgi implementation and phpfastcgi patch

lementation is great, it doesn't need to serve static files. I wouldn't use it for that. James -- James Aylett Chief Technical Architect t 020 7535 9850 f 020 7535 9900 w http://tangozebra.com/ Tangozebra may not be held responsible for the content of this email as it may refle

Re: [PHP-DEV] Re: Using stada...@lists.php.net for spec work

Might I then suggest someone update http://php.net/mailing-lists.php? On Thu, Jul 24, 2014 at 3:38 PM, Sara Golemon wrote: > On Thu, Jul 24, 2014 at 11:24 AM, Stas Malyshev > wrote: > > I would like to propose to use list standa...@lists.php.net (which has > > been dormant since 2009) for PHP

Re: [PHP-DEV] Re: Using stada...@lists.php.net for spec work

Could be. Other then the webform though, I think that's the only place we document where things are happening. On Thu, Jul 24, 2014 at 3:54 PM, Sara Golemon wrote: > On Thu, Jul 24, 2014 at 1:51 PM, James Gilliland > wrote: > > Might I then suggest someone update http:

Re: [PHP-DEV] [VOTE] Mutliple defaults in switch statements

I'm not entirely sure that a backwards compatibility break in a minor release would be considered non-controversial. While this change is pretty trivial, both technically and syntactically, I'm unsure why there even is an RFC process in place if it's going to be ignored because it's "too much trou

Re: [PHP-DEV] Moving multiple defaults in switches RFC back to Under Disucssion.

Oops.. somehow I only sent the reply to Levi.. I blame my phone. Regardless, Thank you for adopting the RFC and setting the status to under discussion from its previous status of "Bike shedding" as I am not sure if per the process we could discuss the merits of the change - only the color of the

Re: [PHP-DEV] RFC: Protocol Type Hinting

wow... why did this just become a measuring contest. Do we need to go recruit people interested and attach their resume's? I'll just toss in I am interested in this. Comparing to current methods of doing this sort of things(because if you're denying it exists in the wild, lets open up some of your

Re: [PHP-DEV] RFC: Protocol Type Hinting

On Thu, Jun 27, 2013 at 10:50 AM, Florin Patan wrote: > On Wed, Jun 26, 2013 at 5:02 PM, Anthony Ferrara > wrote: > > Florin > > > >> Could you please point out what happened in the past 5 months in PHP > >> that changed the landscape so drastically as you say? And don't > >> mention folks reinve

Re: [PHP-DEV] Type hinting/casting request for vote

+1 from me On Tue, Jul 7, 2009 at 1:52 AM, Ilia Alshanetsky wrote: > Last week or so there was a fairly detailed discussion on the internals > list regarding type hinting based on my original patch. Since then the patch > has been revised to address the major concerns that were identified > (bre

RE: [PHP-DEV] Re: Re: PHP Annotations RFC + Patch

I might be wading into this a bit fast but At a very simple level, comments are not meant to be parsed by design. Hence commenting out code so it is not parsed! How would one tell the parser not to read docblock annotations as there wouldn't be a mechanism to comment them out? Lots of peopl

[PHP-DEV] More formal feature request cycle

do a fair bit to stop anecdotal talk of how many people actually want a feature, and stop the list retreading the same arguments over and over again. Have no idea just yet what this would look like, but an thinking something between launchpad and the current php wiki. -- James Butler Sent

RE: [PHP-DEV] Re: PHP Annotations RFC + Patch

+1 for annotations -1/2 for parsing comments - it just doesn't seem right -Original Message- From: Zeev Suraski [mailto:z...@zend.com] Sent: 16 September 2010 17:01 To: Guilherme Blanco Cc: Gustavo Lopes; Derick Rethans; internals@lists.php.net Subject: Re: [PHP-DEV] Re: PHP Annotations

RE: [PHP-DEV] docBlock Parser RFC

on top annotations (or another RFC and do it properly) and anything else they wanted without having DocBlock parsing explicitly tied to annotations (which the internals thread seems have cemented in everyone's mind). James -- PHP Internals - PHP Runtime Development Mailing List To unsubs

Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

I'll bite. Why should this be changed? Is it broken? Is it something that 1 second on google can't answer? If somebody is advanced enough to be using classes (I think about the only time you would use a double colon) then they should know what it means. -- James Butler Sent from my

Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

t be prepared to learn and use domain specific language/terms/acronyms. The double colon is example of this. We can lead the horse to water, but we can't make him drink. -- James Butler Sent from my iPhone > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe

Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

ple not knowing what the error means. -- James Butler Sent from my iPhone -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

possibly suggest a better solution or be won round. (although internals isn't the place for that really) This is not meant to bait but possibly an improvement in your support process or docs might yield a solution? -- James Butler Sent from my iPhone On 30 Oct 2010, at 17:51, "Chad Emr

Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

>From a completely separate stand point. The ability to customise what token >names show up as in an error seems like a much better solution -- James Butler Sent from my iPhone On 30 Oct 2010, at 21:41, "Chad Emrys" wrote: > On 10/30/2010 03:32 PM, Etienne Kneuss wrote: &g

Re: [PHP-DEV] RE: [SPAM] Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

+1 This solves lots of other problems we have and will have in the future. -- James Butler Sent from my iPhone On 1 Nov 2010, at 12:00, "Stefan Marr" wrote: > > On 01 Nov 2010, at 12:06, Alexander Schrijver wrote: >> Its a minor change and an annoyance to a lot

RE: [PHP-DEV] RE: [SPAM] Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

-Original Message- From: Alexander Schrijver [mailto:alexander.schrij...@gmail.com] Sent: 01 November 2010 12:19 To: Stefan Marr Cc: Dennis Haarbrink; Stan Vass; internals@lists.php.net Subject: Re: [PHP-DEV] RE: [SPAM] Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON On M

RE: [PHP-DEV] More formal feature request cycle

ds to move somewhere else, let me know Regards, James -Original Message- From: Stas Malyshev [mailto:smalys...@sugarcrm.com] Sent: 16 September 2010 18:56 To: Christian Kaps Cc: Frederic Hardy; James Butler; internals@lists.php.net Subject: Re: [PHP-DEV] More formal feature request cycl

Re: [PHP-DEV] [PATCH] lenient datetime

Like the idea, Couple of questions... What would happen if the string contained a matching pattern twice or me, which would be 'returned', also does this allow the rest of the string to be pretty much junk. (haven't had time to test patch as miles from a computer) -- James B

Re: [PHP-DEV] More formal feature request cycle

Ah-ha, excellent. I'll get reading. With the the current 5.3.4 effort occupying peoples time and other constraints I'll probably leave proposing anything until the new year. If anyone has any suggestions in the meantime I'd be glad to hear them. James B On 6 Nov 2010, at 02:11,

Re: [PHP-DEV] [PHP] multiple sapi (multiple bug reports)

have been compiling binaries separately already. -- James Butler Sent from my iPhone On 12 Nov 2010, at 22:58, "Jani Taskinen" wrote: > I updated the patch: > > http://pecl.php.net/~jani/patches/multi-sapi.patch > > Now it will fail if no sapi/binary is selected.

Re: [PHP-DEV] GPU Acceleration

language isn't going to be as efficient (yet? :-) ) as C or machine code and therefore you will lose some/alot of the advantage of going GPU. However that is not a reason not to have a go (fork maybe?), something cool may come about from it. Nothing ventured, nothing gained. -- James Butler

RE: [PHP-DEV] Magic quotes in trunk

+1 for removal, magic quotes stopped being a 'good' thing to do back when I first learnt what echo did. Web hosts etc have plenty of version numbers to catch up on/upgrade too before they get to this being a problem. (well most anyway) -Original Message- From: ka...@php.net [mailto:kall

RE: [PHP-DEV] Magic quotes in trunk

ed (shudder), Its going to have go at some point and it would seem daft to try and wait until every app written that requires it to die out. And the longer the feature is on/usable, the more new code written that might really on it. Just my 2 cents James -Original Message- From: Johannes

RE: [PHP-DEV] Magic quotes in trunk

The only problem I can see with this is... do we wait for PHP6 as it seems to be becoming a bit of a Perl 6 (sorry for bringing this up)? I completely agree with it should only happen with major version change and most people won't see 5.x -> 5.y being a major change and therefore the end user e

RE: [PHP-DEV] [RFC] Release Process

asier for new people to get up to speed and reduce the arguments over what the agreed method of doing X is. James -Original Message- From: i...@tyrael.hu [mailto:tyr...@gmail.com] On Behalf Of Ferenc Kovacs Sent: 23 November 2010 14:10 To: Derick Rethans Cc: Felipe Pena; internals Subjec

RE: [PHP-DEV] [RFC] Release Process

-Original Message- From: Matthew Weier O'Phinney [mailto:weierophin...@php.net] Sent: 23 November 2010 14:18 To: internals@lists.php.net Subject: Re: [PHP-DEV] [RFC] Release Process On 2010-11-23, Derick Rethans wrote: > On Tue, 23 Nov 2010, Ferenc Kovacs wrote: > > > All the rest you

RE: [PHP-DEV] Re: Hold off 5.4

Slightly brambly thoughts... I think (imho) the PHP6 hype in user land died down long ago after it became obvious it wouldn't materialise any time soon. It would be nice to see 6 to appear if only to break the (apparent) deadlock that the Unicode stuff brought on(I realise this is not enough jus

Re: [PHP-DEV] RFC: Making T_FUNCTION optional in method declarations

personal view though) -- James Butler Sent from my iPhone On 28 Nov 2010, at 14:02, "Daniel Convissor" wrote: > Hi Again: > > On Sat, Nov 27, 2010 at 08:43:40PM -0500, Daniel Convissor wrote: >> >> Not that my vote really counts, but -1. Doing so would elimin

Re: [PHP-DEV] Re: Hold off 5.4

Following that logic, they will expect the next major version number, whatever it is, to have Unicode. Nothing can be done about that apart from telling the world it won't, including it in, or let them find out for themselves... -- James Butler Sent from my iPhone On 2 Dec 2010, at

Re: [PHP-DEV] Re: Hold off 5.4

On 2 Dec 2010, at 19:46, "Christopher Jones" wrote: > > > On 12/02/2010 11:23 AM, James Butler wrote: >> Following that logic, they will expect the next major version number, >> whatever it is, to have Unicode. Nothing can be done about that apart from

RE: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only

+1 million because GLOBAL scope is horrid (generally) and is thoroughly abused -1 million because it will be the most horrific BC break since time began and I imagine it will break so much code that is currently in the wild... In short I like it but I'm not sure how it would ever get implemented

RE: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only

-Original Message- From: Andrey Hristov [mailto:p...@hristov.com] >James Butler wrote: >> +1 million because GLOBAL scope is horrid (generally) and is thoroughly >> abused >> -1 million because it will be the most horrific BC break since time began >> and

RE: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only

-Original Message- From: Ilia Alshanetsky [mailto:i...@prohost.org] On Thu, Dec 9, 2010 at 5:14 AM, Andrey Hristov wrote: >  Hi guys, > the topic says most of it. What do you think about deprecating the global > keyword and $GLOBALS with it? Together with this making $_REQUEST, $_GET an

RE: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only

In short: Globals can be bad, but not always, it depends on the situation PHP is about getting stuff done... It gives developers the rope, if they want to hang themselves thats up to them. If PHP was designed tomorrow, it might not have globals. but it does, they are in use and removing them be

RE: [PHP-DEV] PHP Performance in Apache: Multi-Process vs Multi-Threaded

imple PHP scripts to test against. Oddly we haven't noticed such a speed increase when benchmarking a Zend Framework based app, but that might be down to application oddities rather than anything else (more work/investigation needed here!). Hope this is helpful. James -- PHP Internals

Re: [PHP-DEV] [PATCH] Add option to disable POST data processing

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 proposa

Re: [PHP-DEV] [PATCH] Add option to disable POST data processing

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

RE: [PHP-DEV] [PATCH] Add option to disable POST data processing

> -Original Message- > From: Daniel Convissor [mailto:dani...@analysisandsolutions.com] > > 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 f

RE: [PHP-DEV] RFC - MACRO

-Original Message- > From: Mathias Grimm [mailto:mathiasgr...@gmail.com] > People always will want more, but some features are nice. > for C/C++ programmers, macro is on of the best things to make thing work > every where. > > its possible to create a IDE macro, but the native php featur

Re: [PHP-DEV] [RFC] Release Process

they could be made a bit more lightweight but otherwise are pretty useful and transparent. -- James Butler Sent from my iPhone > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] PHP Patch for loadHTML options

I've included a patch for review adding the ability to optionally pass options to the DOMDocument::loadHTML[File] functions diff -ru php-5.3.5.orig/ext/dom/document.c php-5.3.5.new/ext/dom/document.c --- php-5.3.5.orig/ext/dom/document.c 2010-04-02 14:08:15.0 -0600 +++ php-5.3.5.new/ext

Re: [PHP-DEV] PHP Patch for loadHTML options

t loose it :) > > thanks for your work! > > Cheers, > > On Thu, Feb 17, 2011 at 12:57 AM, James Devine wrote: >> I've included a patch for review adding the ability to optionally pass >> options to the DOMDocument::loadHTML[File] functions >> >> >

Re: [PHP-DEV] PHP Patch for loadHTML options

on't have to extra define the ones already defined in > xmlParserOption , eg XML_PARSE_NOERROR, but there's no compagnion to > HTML_PARSE_NODEFDTD and HTML_PARSE_NOIMPLIED > > chregu > > On 17.02.11 16:29, James Devine wrote: >> Will do, thanks! >> >> On Thu, Feb 17, 2011 a

  1   2   >