Re: Documenting Namespace (Was Late FQCN resolution using ::class)

From: Date: Tue, 26 Feb 2013 10:02:54 +0000
Subject: Re: Documenting Namespace (Was Late FQCN resolution using ::class)
References: 1 2 3 4 5 6 7  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
hi Lester,

Please stop hijacking threads with all possible off topics and to use
uppercase to improve your arguments (or lack of).

Thanks for your understanding, take #42.

On Tue, Feb 26, 2013 at 11:01 AM, Lester Caine <[email protected]> wrote:
> Benjamin Eberlei wrote:
>>
>> Sorry, forgot to post inline. Thanks for mentioning it and doing it wrong
>> yourself, made me laugh ;-) But you are right.
>
>
> Actually if you check, it was quoted in the right place ;)
>
> But it is getting VERY annoying that a few people choose to ignore the lists
> requested style and blindly top post even when the discussion is nicely
> interleaved. It just does not work in these sort of discussions? :(
>
> I'd missed the significance of the initial thread but the problems of now
> documenting these sorts of 'changes' to language does need to be addressed?
> HOPEFULLY without forcing 'annotation' on us when there is already many
> years of good quality docblock documentation in many major libraries?
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>



-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org


Thread (16 messages)

« previous php.internals (#66236) next »