Are you interested in working together on some patches? I am trying to
write a patch for function return value type hinting as well as class
property type hinting. Maybe even regular variable type hinting if
possible.
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> I'm monitoring
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, second time me ...
Markus Fischer wrote:
> Hi Greg,
>
> Greg Beaver wrote:
>> It is technically possible to fix this, on first glance it would involve
>> having the lexer return a T_STRING for any non-whitespace following
>> T_INTERFACE or betwee
On Dec 31, 2007 6:06 PM, Greg Beaver <[EMAIL PROTECTED]> wrote:
> Marcus Boerger wrote:
> > Hello Johannes,
> >
> > I agree with Pierre here. How about finally making SPL built in always
> > like ext/standard?
>
> +1
>
>
Finally...
+1
> --
> PHP Internals - PHP Runtime Development Mailing List
Marcus Boerger wrote:
> Hello Johannes,
>
> I agree with Pierre here. How about finally making SPL built in always
> like ext/standard?
+1
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm monitoring this subject closely because for me and my inner Zen,
having type hint next to namespaces is one of *the* things I'm looking
forward.
Now the current subject was only about return values, for me I'm looking
for the big picture,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Greg,
Greg Beaver wrote:
> It is technically possible to fix this, on first glance it would involve
> having the lexer return a T_STRING for any non-whitespace following
> T_INTERFACE or between T_IMPLEMENTS and '{'. It would also need to
> return
Hello Johannes,
I agree with Pierre here. How about finally making SPL built in always
like ext/standard?
marcus
Monday, December 31, 2007, 7:31:40 PM, you wrote:
> On Dec 30, 2007 6:58 PM, Marcus Boerger <[EMAIL PROTECTED]> wrote:
>> Hello Andrew,
>>
>> SPL simply allows two things:
>> a
On Dec 30, 2007 6:58 PM, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> Hello Andrew,
>
> SPL simply allows two things:
> a) a stack that hooks into __autoload
> b) a default implementation that may be used (with ot without the former)
>
> We try to group functionality into extensions where we seem
Hello Ryusuke,
generally I like both. But could you provide separate patches?
marcus
Friday, December 28, 2007, 5:45:03 PM, you wrote:
>>any idea about the possibility of hash conflict?
> How about this patch?
> http://www.opendogs.org/pub/php-5.3dev-071228a.patch
> This patch is PHP 5.3 ve
Markus Fischer wrote:
> Hi,
>
> I started a scratch project with this patch and working with it seems
> intuitive so far.
>
> My only question at the moment is the following, however I guess it
> isn't specific to your NS patch then to Dmitry's:
>
> My current practice to declare an interface an
Hello Andrew,
SPL simply allows two things:
a) a stack that hooks into __autoload
b) a default implementation that may be used (with ot without the former)
We try to group functionality into extensions where we seem fit. And by the
time I implemented spl_autoload stuff it made sense to put it i
Hello Sam,
we actually thought of doing it, yes. And apparently I wanted to do
something but I didn't find any time in the past year to be honest.
marcus
Thursday, December 27, 2007, 7:17:16 PM, you wrote:
> I read that type hinting for function return values was going to be
> implemented, is
Also, it will allow PHP applications to recover more gracefully from this sort
of error.
A properly designed PHP application that already has global catch blocks and
some 500 error pages will have this sort of
error come under that same error handling process rather then give an ugly
blank page
On 2007-12-31 12:44, Jani Taskinen wrote:
> We have caught several actual bugs because of NOT using -n as people
> have had exotic settings not included in the stock php.ini files.
I've never doubt that. It certainly has its advantages as well.
> On Sun, 2007-12-30 at 14:47 +0100, Christian Hoffm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 31 December 2007 13:48:52 Antony Dovgal wrote:
> Changing PHP's behavior in a backward-incompatible way that would affect
> everyone and *forcing everyone* to use exceptions seems to be really bad
> idea, especially taking into account that y
> There is no need to implement __call() in every class,.
> Just make sure their parent class implements it.
Yes, I'm well aware of that - but that doesn't really help when taking
into account 3rd party libraries or places where it's not possible
because you don't have control over the base class.
On 31.12.2007 15:09, Fredrik Holmström wrote:
>> 2007/12/31, Mikko Koppanen
>> Calling methods without knowing that they exist sounds like a hack to me.
>> How about using abstract classes or interfaces?
>
> If you look at, for example, python - calling methods that don't
> *know* exists is commo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I started a scratch project with this patch and working with it seems
intuitive so far.
My only question at the moment is the following, however I guess it
isn't specific to your NS patch then to Dmitry's:
My current practice to declare an inter
> 2007/12/31, Mikko Koppanen
> Calling methods without knowing that they exist sounds like a hack to me. How
> about using abstract classes or interfaces?
If you look at, for example, python - calling methods that don't
*know* exists is common practice, it's not a hack from my point of
view. It's
I will be out of the office starting 24/12/2007 and will not return until
02/01/2008.
I will have no email access during this time. I will respond to your email
asap on my return.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
> Yes, I'm aware of call() but it's very slow. Also it's not feasible to
> have
> *all* my classes extend a base class with the a call containing a throw
> InvalidMethodException, and what if I need to use 3rd party libraries that
> make use of call in some other way. __call() is a hack, that, at
On Sun, 2007-12-30 at 14:47 +0100, Christian Hoffmann wrote:
> problems unfixed. Just consider the following scenario: You've got an
> existing PHP installation. Let's assume you are using Apache w/ a
> multi-threaded mpm and as such have built php with zts. All your
> extensions are built with zen
>What is wrong with __call() ?
>See:
>http://www.php.net/manual/en/language.oop5.overloading.php
Hi!
Yes, I'm aware of call() but it's very slow. Also it's not feasible to have
*all* my classes extend a base class with the a call containing a throw
InvalidMethodException, and what if I ne
On Sun, 2007-12-30 at 14:47 +0100, Christian Hoffmann wrote:
> I'd be happy to know what php developers would suggest as a proper fix
> for this problem, if they consider "php -n" wrong.
We have caught several actual bugs because of NOT using -n as people
have had exotic settings not included in t
On Mon, Dec 31, 2007 at 12:28:23PM +0100, Fredrik Holmström wrote:
> Hi!
>
> I've never posted on internal before, but I've been a long time reader
> of it. I've been using PHP for a long time, I think it all started
> back in 2000 sometime, anyway - this is hardly a place to put my
> entire php b
Hi!
I've never posted on internal before, but I've been a long time reader
of it. I've been using PHP for a long time, I think it all started
back in 2000 sometime, anyway - this is hardly a place to put my
entire php biography up for show, so I'll jump right to the action.
Ever since PHP5 and th
There is "how-to" in Sara's book
And for examples check "sapi" folder of php distribution.
On 12/31/07, Talya Nevo <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am porting my software from Linux to µC/OS-II OS.
> On Linux I ran the Boa Web server with PHP.
> The µC/OS-II has a basic open source Http Se
PHP 6 Bug Database summary - http://bugs.php.net
Num Status Summary (64 total including feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
===
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (624 total including feature requests)
===[*Compile Issues]==
43389 Open configure ignoring --without-cdb flag
===[Apa
Hi,
I am porting my software from Linux to µC/OS-II OS.
On Linux I ran the Boa Web server with PHP.
The µC/OS-II has a basic open source Http Server that does not support PHP or
CGI.
What I was able to do - is from the Http server, each time an http request is
received, call using 'System' fun
30 matches
Mail list logo
