Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66262
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.48 as permitted sender)
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: internals@lists.php.net
References: <AB950117-17A2-4729-8CB0-0C5CACE0B20C@me.com>
Date: Wed, 27 Feb 2013 12:18:34 +0400
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Message-ID: <op.ws5n08ogc9evq2@nikita2206-n56vj>
In-Reply-To: <AB950117-17A2-4729-8CB0-0C5CACE0B20C@me.com>
User-Agent: Opera Mail/12.14 (Linux)
Subject: Re: [PHP-DEV] I would like to write an RFC for the addition of an
 internal keyword
From: inefedor@gmail.com ("Nikita Nefedov")

On Wed, 27 Feb 2013 11:07:06 +0400, Jens Riisom Schultz <ibmurai@me.com>  
wrote:

> Hi,
>
> I just want to get a feel for whether the following idea would be  
> instantly rejected (for example I get the feeling that adding keywords  
> is a big deal):
>
> Often, when writing frameworks, you need to make public or protected  
> functionality or classes which should only be called from inside the  
> framework. You CAN ensure this with a lot of ninja tricks and  
> debug_backtrace, but it is very cumbersome and often hides your methods  
> and properties from class signatures.
>
> Therefore I would propose adding a C# style "internal" keyword. (  
> http://msdn.microsoft.com/en-us/library/7c5ka91b(v=vs.80).aspx )
>
> The idea is, simply, that functions, methods and classes marked as  
> "internal" would only be accessible from within the namespace in which  
> they are defined.
>
> For example the following class, "namespace Framework; internal class  
> Something {}", would only be visible from within the "Framework"  
> 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
>

Hi,
I, for one, think it should be solved on the IDE side. I used a lot of  
Doctrine's internal methods lately and if they would be not accessible I  
wouldn't be able to do a lot of things.
Of course internal methods/classes shouldn't be exposed as a part of API,  
but if they exist, I would want to call them *if I know what I'm doing*. I  
think it would be useful if phpdoc had an @internal tag so that IDEs could  
highlight places where you use internal parts of library.