On Wed, Jan 21, 2015 at 12:21 PM, Tony Marston
wrote:
>
>
> Because I would rather fight for valid principles than give in. To quote
> Emiliano Zapata "It is better to die on your feet than live on your knees".
I don't think constructors are what he had in mind.
tually remove it.
On Wed, Jan 21, 2015 at 9:50 AM, Tony Marston
wrote:
> "Kristopher" wrote in message news:CAF9U7z-bkYRDwAL8CA4_=
> 1dhorl0evp_mzwf6qwqscwdf7n...@mail.gmail.com...
>
>>
>> On Tue, Jan 20, 2015 at 8:26 AM, Tony Marston
>> wrote:
>>
&
On Tue, Jan 20, 2015 at 8:26 AM, Tony Marston
wrote:
@tony: What's really interesting is that all this time you've spent arguing
could have been used to update your code and make this no longer an issue
for you.
@everyone: Would an RFC be necessary to update the PHP manual to actually
recommend
On Tue Nov 04 2014 at 9:31:06 AM Lester Caine wrote:
>
> Every IDE I've used has always working nicely with docblock annotation
> and typing and has provided the facilities people seem to think should
> be built in to PHP.
>
You understand you don't have to use these new features, right? You can
On Tue, Oct 14, 2014 at 9:25 AM, Andrea Faulds wrote:
>
> Let’s add $_REQUEST_BODY and $_QUERY_STRING and make them aliases of $_GET
> and $_POST then. Because they’re aliases (by-reference superglobals),
> there’s no additional memory consumption, but we finally have saner names.
>
>
$_HTTP_REQUE
Instead of endless, useless bickering, how about everyone both for and
against merging jump in and start helping with phpng (docs, api
cleanup/stabilization, but fixes, etc)?
Imagine how much more stable and ready to merge it would be if you
concentrated the saber rattling energy towards actually
On Mon, Jul 14, 2014 at 1:14 PM, Alain Williams wrote:
> On Mon, Jul 14, 2014 at 06:09:22PM +0100, Andrea Faulds wrote:
> >
> > On 14 Jul 2014, at 18:01, Alain Williams wrote:
> >
> > > But if you have:
> > >
> > >function foo(int $a) {
> > >...
> > > $a = 3 / 2;
> > >}
> > >
On Tue, Sep 24, 2013 at 8:25 AM, Terence Copestake <
terence.copest...@gmail.com> wrote:
> Playing devil's advocate here, could this feature make the language more
> expressive?
>
> Take for example an API where you'd typically wrap a method call in
> try/catch blocks to handle the various "outcom
On Wed, Sep 18, 2013 at 2:25 PM, Daniel Convissor <
dani...@analysisandsolutions.com> wrote:
> As someone who writes a lot of open source (and proprietary) code that
> gets run on machines that I have no control over, implementing this
> proposal will complicate my life. Every time I make a funct
