On Fri, 12 Jul 2013 02:47:34 +0200
Johannes Schlüter wrote:
> On Fri, 2013-07-12 at 08:10 +0900, Kenji Suzuki wrote:
> > On Thu, 11 Jul 2013 23:45:02 +0200
> > Johannes Schlüter wrote:
> >
> > > Please Note: This will be the last regular release of the PHP 5.3
> > > series. All users of PHP are
On Fri, 2013-07-12 at 08:10 +0900, Kenji Suzuki wrote:
> On Thu, 11 Jul 2013 23:45:02 +0200
> Johannes Schlüter wrote:
>
> > Please Note: This will be the last regular release of the PHP 5.3
> > series. All users of PHP are encouraged to upgrade to PHP 5.4 or PHP
> > 5.5. The PHP 5.3 series will
On Thu, 11 Jul 2013 23:45:02 +0200
Johannes Schlüter wrote:
> Please Note: This will be the last regular release of the PHP 5.3
> series. All users of PHP are encouraged to upgrade to PHP 5.4 or PHP
> 5.5. The PHP 5.3 series will receive only security fixes for the next
> year.
The exact date of
The PHP development team announces the immediate availability of PHP
5.3.27. About 10 bugs were fixed, including a security fix in the XML
parser (Bug #65236).
Please Note: This will be the last regular release of the PHP 5.3
series. All users of PHP are encouraged to upgrade to PHP 5.4 or PHP
5.5
On 7/11/13 2:56 PM, Florin Patan wrote:
We already have a bunch of RFCs about strict typing in PHP:
https://wiki.php.net/rfc/typechecking
So I personally am not sure we need yet another RFC on the topic - given
that we discussed previous ones multiple times.
You are right, as part of the mov
> @Sara: thank you for the offer, I'll send you a mail, if it's ok with
> you, in the next days, I'd want to make this as a tutorial and maybe
> me implement it with your guidance, but more on this another time.
>
> Sure thing. PHP needs more developers with deep understanding of the
engine. I'd
On Thu, Jul 11, 2013 at 10:52 PM, Sara Golemon wrote:
> I agree 100%.
>
> This particular item has been in the works since before I joined the team
> and I've given them a bollocking out over it. You may have noticed
> UConverter and a few other changes which WERE proposed to internals@ prior
> t
I agree 100%.
This particular item has been in the works since before I joined the team
and I've given them a bollocking out over it. You may have noticed
UConverter and a few other changes which WERE proposed to internals@ prior
to inclusion in HHVM and the implementation of those features were
>
> > 1) HHVM isn't just running FB. A number of sites have either already
> started using HHVM, or intend to soon.
>
> Were could I read about those?
>
> I didn't list any because I don't know how they individually feel about
sharing that info. I realize that takes the wind out of my statement,
On Thu, Jul 11, 2013 at 10:27 PM, Sara Golemon wrote:
> I won't suggest that PHP should follow HHVM, if anything I'll usually (and
> have frequently) rallied for the other way around. In this case, however,
> as with Generators, I think that we should endeavor to keep the
> implementations close
If you run into issues (yes, our build system still sucks a bit) poke me in
IRC freenode/#hhvm (or ptarjan or any other @ in that channel).
And just to jump in front of what I detect in your comment "albiet compile
it". Repeat: HHVM is not a code translator anymore. Hasn't been for
awhile now.
Hi!
> 1) HHVM isn't just running FB. A number of sites have either already
started using HHVM, or intend to soon.
Were could I read about those?
> 2) The "static compilation" description is grossly outdated information.
I guess my knowledge about HHVM is a bit out of date, which is no wonder
a
> Should I conclude that there's enough interest for this feature and
> move from a gist to a RFC? If so, I would definitely need someone to
> help out with the implementation.
>
> Without wanting to put the cart too far before the horse, I'll mention
that FB is willing to offer resources (me, basi
> While HHVM is a very interesting project, their use case is pretty
> specific and narrow, and, as I understand, connected to a single
> application (albeit running huge traffic numbers). So I'm not sure
> copying whatever they do is necessarily good for PHP as a whole. HHVM
> case is basically st
Hey,
On Thu, Jul 11, 2013 at 9:51 PM, Stas Malyshev wrote:
> Hi!
>
>> Thanks for your input Sara, everything sounds very interesting. In all
>> fairness I haven't looked at HHVM but I from what you described about
>> this particular feature sounds good.
>>
>> Should I conclude that there's enough
Hi!
> Thanks for your input Sara, everything sounds very interesting. In all
> fairness I haven't looked at HHVM but I from what you described about
> this particular feature sounds good.
>
> Should I conclude that there's enough interest for this feature and
> move from a gist to a RFC? If so, I
On Wed, Jul 10, 2013 at 10:58 AM, Patrick ALLAERT
wrote:
> Hello Florin,
>
> 2013/7/10 Florin Patan :
>> Since you brought up the discussion, would you think it would make
>> more sense to actually start and integrate HHVM into PHP rather that
>> patching it up?
>> Or better yet, rewrite it with a
On Wed, Jul 10, 2013 at 8:30 PM, Sara Golemon wrote:
>> With regard to any sort of hinting, an issue of 'one of' return types
>> would need to be addressed (I hope).
>>
>> function foo(SomeClass $bar, int $baz) : bool, SomeClass {}
>>
>> Allowing for a failure (False) or a success (SomeClass).
>>
18 matches
Mail list logo
