or classes which should only be called from inside the
framework.
Here I'd like to throw Design by Contract at you:
http://en.wikipedia.org/wiki/Design_by_contract
I'll have to read up on that. ;)
Cheers,
Fabian
On 02/28/2013 07:56 AM, Jens Riisom Schultz wrote:
Hi everyone,
(I
Setting aside difficulty of implementation, I'm coming around to the idea,
though I think you could simplify it by cordoning off an entire namespace.
E.g.:
A namespace at least two deep (e.g. \A\B\) may be marked 'protected' (by some
method TBD). Classes and functions declared in a
writing it off.
...And a question: Am I wrong when I assume that this should be relatively
easy to implement?
-Jens Riisom Schultz
On Feb 27, 2013, at 10:11 AM, Lazare Inepologlou linep...@gmail.com wrote:
Hello,
2013/2/27 Jens Riisom Schultz ibmu...@me.com
Hi,
I just want to get a feel
this information on a per file
basis.
On Tue, Feb 26, 2013 at 8:25 AM, Jens Riisom Schultz ibmu...@me.com wrote:
Ok I get that, thankyou for the explanation.
static::class is not an option. I'm trying to resolve class names defined in
docblocks, since phpdoc2 allows for entering type hints (classes
namespace.
I have a hunch that this would be relatively easy to implement.
If noone objects I would attempt to create a patch and an RFC.
What do you think?
-Jens Riisom Schultz
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
that is weird.
I guess what I'm trying to ask is whether it would be impossible to support
late FQCN resolution in any way? It would be very useful for frameworks to be
able to do this.
- Jens Riisom Schultz
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
I could look into it and try to write a patch... Because I think this
would be really useful for framework developers, php unit testing and php doc
for example.
-Jens
On Feb 25, 2013, at 11:20 AM, Nikita Nefedov inefe...@gmail.com wrote:
On Mon, 25 Feb 2013 14:00:04 +0400, Jens Riisom Schultz
