Hello all. I'd like to start by saying that I am by no means an expert on the
subject at hand, and my knowledge is limited to pretty much basic C/C++. I have
done little more than patch and write ad hoc extensions for PHP in the past.
I'm not looking to criticize so much, as I'm just interested
I will also note that my phone cut off the part about this post not being
serious.
I, however, have no sense of humor.
On Jul 18, 2012, at 11:17 PM, Ronald Chmara wrote:
> With PHP 6, lets start with a:
> Pure
> Object
> Oriented
> PHP
>
> ...idea, and extend it out, so we can have a:
> Stru
I'll start off by saying that I am, personally, a great fan of OO. Pure OO
languages have always tickled me just right.
But I question the idea that making something pure OO makes it better. And in
PHP, it wouldn't be a mere revamp of the OOP system like php5 did, it would
fundamentally change
While it's not the prettiest of side effects in php, I don't agree it should be
"fixed"
On top of a massive BC break, it's not as if the results are inconsistent.
Learning php means learning how type juggling works.
At most, I'd remove the part that truncates numeric strings like "123abc" and
I once pushed this hard for namespaces. Then, after years of it being shot
down, they did it.
And now I'm sad. It didn't occur to me until after it had been implemented how
bad an idea it was for php. I think this is one of those times.
Type hinting is wonderful, but i'm not sure you could rea
+1
On Jun 5, 2011, at 6:02 PM, Pierre Joye wrote:
> test for brain dead SURBL
>
> --
> Pierre
>
> @pierrejoye | http://blog.thepimp.net | http://www.libgd.org
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
--
PHP Inte
The issue I have with that is that, regardless of the syntax chosen, even if it
meant a 100% inline JSON syntax, you would still (for obvious reasons) need to
parse any JSON string into PHP structures. You still have to do
json_load($php_or_json_string) or (god have mercy) eval($string). At that
Would it be possible to have a vote on the various options being proposed here?
I think JSON syntax is definitely more concise and easier to type, as well as
more convenient -- but I don't think it makes sense for PHP without changing
how arrays work (I'm all for that, but that's a different dis
Exactly my point. Why try to fudge json into php, instead of just improving php?
On May 31, 2011, at 5:02 PM, Dan Birken wrote:
> Yes it does :)
>
> I guess my point was it would be confusing if PHP supported JSON-like
> syntax, but json_decode(X) was different from eval(X). So if PHP isn't
> g
Would seem to me a more elegant solution would to just drop the idea of json
interoperability and go with something that works for PHP.
('a'=>'b', 0=>1234) perhaps?
On May 31, 2011, at 4:45 PM, Ilia Alshanetsky wrote:
> Rasmus,
>
> Don't you think having support for both ['a':1, 'b':2] and {'
)
On Apr 30, 2011, at 1:44 PM, Ferenc Kovacs wrote:
>
>
> On Sat, Apr 30, 2011 at 8:16 PM, Matt Wilson wrote:
> Really would depend on the user. Part of my company still runs on SQLServer
> 2003, for instance...
>
> Corporate infrastructure rarely sees upgrades. Your cou
Sorry, you're right. It's 2000 service pack 3 :)
On Apr 30, 2011, at 1:44 PM, Ferenc Kovacs wrote:
>
>
> On Sat, Apr 30, 2011 at 8:16 PM, Matt Wilson wrote:
> Really would depend on the user. Part of my company still runs on SQLServer
> 2003, for instance...
>
Really would depend on the user. Part of my company still runs on SQLServer
2003, for instance...
Corporate infrastructure rarely sees upgrades. Your cousin with the wordpress
fetish, on the other hand...
On Apr 30, 2011, at 1:10 PM, Ferenc Kovacs wrote:
> On Sat, Apr 30, 2011 at 7:53 PM, Rasm
om "empty". The implementation in php is slightly difference, since you're
not actually working with, say, a null pointer.
On Apr 28, 2011, at 1:05 PM, Martin Scotta wrote:
>
> Martin Scotta
>
>
> On Thu, Apr 28, 2011 at 2:51 PM, Matt Wilson wrote:
> Here
Here's my issue:
We're borrowing a feature from strongly typed languages and forcing it on a
loosely typed language. I'm fine with this, if we're true to the concept.
In a regular language, if you type something to return an object of type Foo,
you might still get back null, and appropriately n
Something I've been doing for a long time is similar, but in my opinion a much
better practice.
function coalesce(&$val, $ifnull = false)
{
return empty($val) ? $ifnull : $val;
}
Add whatever restrictive logic you wish here, if empty() isn't good enough for
your purposes.
$_GET['might
@.
On Apr 10, 2011, at 9:22 PM, D. Dante Lorenso wrote:
> The problem with implementing "ifsetor", "filled", or "??" in userland is
> that the "not set" or "undefined" warning is fired before the variable is
> passed to the underlying function/method.
>
> Is it possible to add a modifier that
bring back a proposal we had a couple of years ago, to
> > totally disable post data.
>
> Would calling it enable_automatic_post_data_reading help with that
> confusion?
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
Matt Wilson
816.830.9429
So, you decided to jump in to criticize a design decision that went in after
several months of discussion, without any insight into why it was done the way
it was?
On Apr 28, 2010, at 4:45 PM, Sylvain Rabot wrote:
> Hi,
>
> The comment I'm about to make is behind the times, and, now, useless,
I agree, however there are certain aspects of PHP's errors that leave
a lot to be desired. For instance, a failed fopen or a failed socket
will often result in an uncatchable warning from php. Sure, you can
add a @ to the line but that's slow and doesn't tell you anything
about what happene
+1
On Jul 6, 2009, at 7:52 PM, Ilia Alshanetsky wrote:
Last week or so there was a fairly detailed discussion on the
internals list regarding type hinting based on my original patch.
Since then the patch has been revised to address the major concerns
that were identified (breakage of binar
+1000 * infinity plus one
On Jul 1, 2009, at 12:23 PM, Paul Biggar wrote:
Hi Ilia,
This is great.
On Wed, Jul 1, 2009 at 5:59 PM, Ilia Alshanetsky
wrote:
I've taken a few hours this morning to port my 5.2 type hinting
patch to
5.3. In recognition of a need for a more 'flexible' numeric t
I'm not sure if you're looking to change the C implementation or not,
but you could always bypass the internal processing of the file. Set
post_max_size to 0 and parse the HTTP_RAW_POST_DATA manually.
On Jun 2, 2009, at 3:55 PM, Bharat Nagwani wrote:
Hello,
I want to change the way file u
ing(1) "d"
}
On May 31, 2009, at 8:46 PM, Nathan Rixham wrote:
Matt Wilson wrote:
get_class_vars + array_diff
cheers but nope; as the manual says
"Returns an associative array of default public properties of the
class"
need private and inherited private
On May 31,
get_class_vars + array_diff
On May 31, 2009, at 8:04 PM, Nathan Rixham wrote:
Hi All,
hoping somebody can help me here..
I need to implement an inverted __sleep method, by which I mean to
specify what variables should not be included.
use case:
// TODO code return instance properties e
+1 Off (Issue warnings)
On Feb 18, 2009, at 11:34 PM, Eric Stewart wrote:
We seem to have a split opinion on what the production INI value for
allow_call_time_pass_reference should be.
As I understand it, this does not enable or disable the ability to
pass
references at call time. It only en
On Nov 12, 2008, at 1:14 PM, Lukas Kahwe Smith wrote:
Hi,
here are a few questions that need to be answered ASAP.
If at all possible keep your votes as short as possible. I think all
of the above topics have been discussed quite a lot on the list. So
I hope voters can spare the list needl
Documenting the curl_multi_* functions
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I'm curious why this exists. It doesn't seem to do anything but harm?
Not a day goes by where I'm not asked why some one can't get mysql to
work with php because of this thing...
Just wondering why its there, is all.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit
29 matches
Mail list logo
