Hi,
You are making a very huge mistake, IMHO. By having 2 conflicting RFC,
you are taking the risk they both fail. And it won't do any good to the
language.
While you could have either proposed yours after the STH one if it
would have failed, or create a new RFC to make the STH one evolve
if it
Mike Dugan just told me § and £ aren't standard symbols, and he is right, I
didn't have a picture of a standard keyboard when I proposed these symbols
:(
I don't know what could be used instead. Certainly a combination of symbols,
but I can't find one.
Someone got an idea ?
Regards.
Benoit
Hi Patrick,
I don't think it should be implemented. If you are calling a static method
like a non-static method, your code has a problem. I think it would do
more harm than good. Not only for the code comprehension and logic,
but also for the skills of the people who make this mistake.
But I
Hi,
Sebastian B.-Hagensen a écrit dans le message de groupe de discussion :
caojcv8yx7vohtd1ja2obdrntdzb0q1soyqdyhsar3vt2vgs...@mail.gmail.com...
2015-02-13 14:45 GMT+01:00 Thomas Punt tp...@hotmail.co.uk:
Hi Francois,
From: franc...@tekwire.net
May I suggest to extend your proposal to
Hey Tom,
Thomas Punt a écrit dans le message de groupe de discussion
Hey Benoit,
From: bensor...@neuf.fr
Hi,
I agree, this behaviour should be extended to all the is_* functions if
possible.
I'm not sure we can do that for all of the is_* functions, since
is_callable() accepts up to
