Hi Olivier,
Could you be a little more specific about what questions you have? Is it to do
with the licensing or physically how to go about achieving your aim?
Regards,
James
--
James Butler
Sent from my iPhone
On 15 Mar 2011, at 20:02, "Olivier Hoareau" wrote:
> Hi !
>
&
>> Proposal (after five minutes of thought)
>>
>>
>> 1. Public - A class can be instantiated or called statically from
>> anywhere. For reasons of backward compatibility a class without any modifier
>> would be considered public.
>>
>> 2. Internal - A class can only be instantiated/cal
**
On 08/03/11 15:46, Matthew Weier O'Phinney wrote:
> On 2011-03-08, Pierre Joye wrote:
>> On Mon, Mar 7, 2011 at 10:49 PM, Ferenc Kovacs wrote:
>>
>>> From the sideline:
>>> it's hard to belive that there are no one else with opinion on this matter.
>>> I don't want to take sides because I do
Are you using PHP as a module inside a web server such as apache? If so then
module unloading is generally the problem of the web server rather than PHP. Is
(fast) cgi not an option?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
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
-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
> -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
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
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
This is just personal experience and observation but...
We are running Apache Worker with PHP safely by using PHP-FPM rather than via a
shared object, so we don't have to worry about thread safety in the PHP
component but can have apache multithreaded. I realise this isn't actually
multi-threade
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
-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
-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
+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
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
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
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
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
-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
Just a thought from a non-dev
Rules/policies/procedures/process should always be written down or recorded
somewhere, otherwise how do you know what they are? and how do you make sure
changes to those rules are known about?
Having a central place that every can reference (wiki) makes a ton of sen
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
Are the £1 hosting companies going to be using 5.4+ any time soon? I'm still
coming across hosts who still transition 4.X -> 5.1/2.
I think these slow moving hosts are going to form a natural time delay between
any changes now and these changes taking affect on the parts of the user
community wh
+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
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
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.
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, "Herman Radtke"
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
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
-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
+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
>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
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
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
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
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
FWIW, I am in favour of something that allows the parsing of DocBlock comments
(should it just be DocBlock comments though?) and am implementation agnostic so
far (i have too little understanding of where in the core/extensions this would
need to sit).
This would then allow developers to hack o
+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
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
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
39 matches
Mail list logo
