On Thu, Feb 26, 2009 at 8:48 PM, Guilherme Blanco
wrote:
> I doubt you'll find a patch to it.
>
> Mainly, the patch will be against this principle:
>
Hmm, that wouldn't actually have an impact, as (at least, what I'm
aiming for/wanting to do) is not to introduce periods as valid in
actual class
Hi all,
I've been playing around with autoload lately, and specifically using
autoload to load classes which may be in subdirectories. I came up
with the following test script:
The first line demonstrates what I'm after ("autoloading Foo.Bar"),
and the second seems to give a bit of an odd/incor
On Thu, Feb 26, 2009 at 5:21 PM, Moriyoshi Koizumi wrote:
> So, in what point do you guys think of this change as valid?
>
> Moriyoshi
Is there any known examples of code broken by this, or is it a more
academic than practical problem?
--
PHP Internals - PHP Runtime Development Mailing List
T
On Thu, Feb 26, 2009 at 1:58 PM, Rodrigo Saboya
wrote:
> For the average PHP programmer, the language will simply "get faster". That
> can't be bad in any way. It doesn't encourage you to write bad code, it just
> doesn't kick you in the nuts when you do.
It's probably also worth noting that in
On Thu, Feb 19, 2009 at 10:24 PM, Andrei Zmievski wrote:
> Can someone explain why ext/sockets and also stream socket functions care
> about FD_SETSIZE?
They care, because they use the select(2) syscall, which cares about FD_SETSIZE.
--
PHP Internals - PHP Runtime Development Mailing List
To un
On Sun, Jan 18, 2009 at 9:39 PM, Nathan Rixham wrote:
> I've reworded my original mail completely maybe this one will have more
> feedback (or not)
>
> question: Would anybody else like to see, or feel the need for, *optional*
> type hinting of variables and class properties in PHP?
>
I was invol
Ugh. Apparantly I forgot to CC the list on those last two mails..
Sorry. Pasted so others stay in on the conversation:
On Fri, Dec 19, 2008 at 3:18 PM, troels knak-nielsen wrote:
>
That's an interesting mail, expresses a viewpoint I hadn't considered,
so, thanks for that.
However: If PHP provid
On Fri, Dec 19, 2008 at 2:40 PM, troels knak-nielsen wrote:
> PHP is loosely typed. Adding typehints to primitives would change
> this. The only reason that it is working with object types, is because
> you can't automatically coerce object types anyway.
>
> --
> troels
I'm not sure what you are
dy impossible.
If I'm missing something, please let me know :)
On Fri, Dec 19, 2008 at 2:31 PM, Nathan Rixham wrote:
> Robin Burchell wrote:
>>
>> Just a random thought I have from reading over that:
>>
>> Would it not be more 'natural' to change '
It would be a bit more in fitting with traditional languages, and
definitely less typing.. it may require some parser modification,
though..?
(I'd also like to throw my +1 in for scalar type hints, and optional
type coercion for return values - this is something I have run into
annoyances with
Settings which change behaviour like that aren't really all that fun
for third party/portable applications developers, e.g. forum software
and the likes. magic_quotes_gpc and others are good examples of this.
Going back to Rasmus' mail based on his discussion with Douglas, I
think that option #1 (
A unix timestamp is in UTC, offsets are stored and applied seperately.
See tzset(3).
Unless someone has misconfigured their system, that is.
On Fri, Dec 5, 2008 at 10:16 AM, Karsten Dambekalns <[EMAIL PROTECTED]> wrote:
> Hi Derick.
>
> Derick Rethans wrote:
>>
>> This is not the correct thing t
methods is supported and respected, it
seems like a rather strange omission.
Is this perhaps something that would be looked on positively? If so, I
might start trying to look into it in my spare time. (note: advice on
where to look, what not to do, etc are all very much welcome).
Thanks!
Robin Bu
13 matches
Mail list logo
