On Sat, Jul 4, 2009 at 20:15, Sandro Tosi wrote:
> On Sat, Jul 4, 2009 at 18:43, Sean Coates wrote:
>>> Just another question: may you please list me all the possible
>>> 'Status' field values? In particular we are interested in those
>>> 'Status'es that identify the bug as closed and "wontfix".
>>
Hi!
RE your second patch, from http://ilia.ws/patch/type_hint_53_v2.txt
Some notes on this patch:
- I still think the matter of interfaces and inheritance should be dealt
with (and just comparing hints is not enough, it should be full
LSP-compliant check).
- It looks like you can't have c
On 04.07.2009, at 21:10, Paul Biggar wrote:
On Sat, Jul 4, 2009 at 7:12 PM, Lukas Kahwe
Smith wrote:
I can't see the difference between your proposal and the
conclusion I
reached yesterday?
(which was that there is a near consensus around strict checks by
default, with casts allowed with
On Sat, Jul 4, 2009 at 7:12 PM, Lukas Kahwe Smith wrote:
>> I can't see the difference between your proposal and the conclusion I
>> reached yesterday?
>>
>> (which was that there is a near consensus around strict checks by
>> default, with casts allowed with some syntax).
>
> Well to me it Sounded
It should be fine
Ilia Alshanetsky
On 2009-07-04, at 2:49 PM, Paul Biggar wrote:
Hi Ilia,
On Wed, Jul 1, 2009 at 5:59 PM, Ilia Alshanetsky
wrote:
There has been quite a bit of discussion on this list, IRC, developer
meetings, etc... about introduction of type hinting to PHP. Most
peopl
Hi Ilia,
On Wed, Jul 1, 2009 at 5:59 PM, Ilia Alshanetsky wrote:
> There has been quite a bit of discussion on this list, IRC, developer
> meetings, etc... about introduction of type hinting to PHP. Most people
RE your second patch, from http://ilia.ws/patch/type_hint_53_v2.txt
Index: Zend/zen
I can't see the difference between your proposal and the conclusion I
reached yesterday?
(which was that there is a near consensus around strict checks by
default, with casts allowed with some syntax).
Well to me it Sounded like you wanted to Rely on Standard Type juggling
and what i am pro
hi.
On Sat, Jul 4, 2009 at 8:12 PM, Lukas Kahwe Smith wrote:
> Well to me it Sounded like you wanted to Rely on Standard Type juggling and
> what i am proposing is more strict than that. More over i am Not convinced
> that strict should Be the Default.
The default is what we have now (implicit m
On Sat, Jul 4, 2009 at 18:43, Sean Coates wrote:
>> Just another question: may you please list me all the possible
>> 'Status' field values? In particular we are interested in those
>> 'Status'es that identify the bug as closed and "wontfix".
>
> I believe all current statuses are declared here:
>
On 04.07.2009, at 16:05, Paul Biggar wrote:
Hi Lukas,
On Sat, Jul 4, 2009 at 7:20 AM, Lukas Kahwe
Smith wrote:
Last evening I put together a quick proposal for a weak and strict
checking
approach, since I felt that things were being concluded a bit
prematurely.
More importantly I detai
On 04.07.2009, at 14:27, Derick Rethans wrote:
So I would propose to:
1. have ilia's strict typing patch (minus scalar and numeric)
2. have a patch that also adds for casting type hints from your RFC.
Those could (and should) be considered as *two* new features.
As for syntax, I believe the
Hi all,
On Sat, Jul 4, 2009 at 18:20, Sean Coates wrote:
>> so what i'm wondering is: is there an easily parseable or structured
>> interface (xmlrpc, soap, read-only JSON export, whatever) to the php.net
>> bts
>> that could be used to get a bug's information? or would such a bts-link
>> service
Just another question: may you please list me all the possible
'Status' field values? In particular we are interested in those
'Status'es that identify the bug as closed and "wontfix".
I believe all current statuses are declared here:
http://cvs.php.net/viewvc.cgi/php-bugs-web/include/functions.
so what i'm wondering is: is there an easily parseable or structured
interface (xmlrpc, soap, read-only JSON export, whatever) to the
php.net bts
that could be used to get a bug's information? or would such a bts-
link
service need to resort to scraping the page for a particular bug's
status
Hi Lukas,
On Sat, Jul 4, 2009 at 7:20 AM, Lukas Kahwe Smith wrote:
> Last evening I put together a quick proposal for a weak and strict checking
> approach, since I felt that things were being concluded a bit prematurely.
> More importantly I detailed the issues I see with a pure strict type
> che
On Sat, 4 Jul 2009, Lukas Kahwe Smith wrote:
> I am publishing it a bit prematurely imho, but its not without merit
> at this stage either and since I will be busy playing frisbee all
> weekend, I thought I get it out there for people to comment right now:
> http://wiki.php.net/rfc/typechecking
Hello Internals.
I'm a userland PHP developer, I readed all the proposals about type
hinting and did some code writing with type hinting to see how it
looks like. Well, to my understanding it's a mess if both types of
type hinting are done.
Here is an example of a function:
function calculate_age
On Sat, 4 Jul 2009, sean finney wrote:
> so what i'm wondering is: is there an easily parseable or structured
> interface (xmlrpc, soap, read-only JSON export, whatever) to the php.net bts
> that could be used to get a bug's information? or would such a bts-link
> service need to resort to scrapi
hi everyone,
(if there's a better place to ask this, my apologies and feel free to
redirect me!)
does anyone know here if there is any machine-friendly interface to
the php bug tracking system?
in debian we have a service called "bts-link"[1] which we can use to track
"forwarded" bugs in remote
On Jul 3, 2009, at 10:58, Gwynne Raskind wrote:
On Jul 3, 2009, at 11:39 AM, Ryan Schmidt wrote:
On http://www.php.net/manual/en/migration53.sapi.php it says of
PHP 5.3 that "FastCGI is now always enabled and can not be
disabled. See sapi/cgi/CHANGES for more details." The same text
appea
On 7/4/09, Lukas Kahwe Smith wrote:
> Last evening I put together a quick proposal for a weak and strict checking
> approach, since I felt that things were being concluded a bit prematurely.
> More importantly I detailed the issues I see with a pure strict type
> checking only approach.
Thanks f
21 matches
Mail list logo
