Class names MUST be declared in StudlyCaps.
--To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/4d6608e9-f5f3-4251-bfa0-f1f343cde3d0%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
Also note the bylaw for naming things that FIG adopted for its own use -- https://github.com/php-fig/fig-standards/blob/master/bylaws/002-psr-naming-conventions.md
CRB
Psr\
namespace which means that you don't need Interface
in the name to avoid conflicts, either. It makes for longer names and makes for more cumbersome communication. See: https://github.com/php-fig/fig-standards/pull/244/files#r8744476 and related conversation.--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/848e1f68-9997-40b3-b305-a9b3e5cd0e2f%40googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/php-fig/10lM-UNudvU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to php-fig+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/52CE44EE.40704%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/52CE44EE.40704%40gmail.com.
On Wednesday, January 8, 2014 10:08:48 PM UTC+1, Phil Sturgeon wrote:PSR-1 definitely says:Class names MUST be declared in StudlyCaps.Sorry, you'll have to go with the suffix approach.
Yes, that's why I wanted this to be considered for a new PSR, and it needn't be a MUST, MAY is enough.
For example, if you have a file called UserInterface.php. Can you tell from the name alone does it contain a PHP interface with some common methods for different user classes (like for CMS users and frontend users) or does it contain a class which implements some kind of a user interface (GUI or something)?
If the small-caps prefix were to be allowed, it would be obvious that the file iUser.php contains the first, and UserInterface.php the second.
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/571d38fd-e368-4f68-861d-ff43b3f51e7b%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/FDC2A9B8-6557-43A2-A785-4C58E856FF23%40gmail.com.
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/4ebed995-dbc8-4a8a-816e-0244f22eb5ba%40googlegroups.com.
Right, Marko asked a simple question and got a simple answer, then this was "hijacked" by folks injecting their personal preference into the discussion.
There is no PSR for specific naming of interfaces, traits, etc, but PSR-1 definitely says StudlyCaps, so do that and you're golden. WE use a naming convention, and should continue to use that naming convention. PHP itself has a different naming convention each day of the week, which we won't be copying. FooInterface, BarTrait, is in the bylaw and we should absolutely stick to that.
We've already decided in our bylaws on how our code will be named, let's not revisit it.
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/d3122219-11a3-475a-9c2d-a02b4b85f147%40googlegroups.com.
Hi Moisa,
As far as I can see Marco his question was answered in the first two replies before the thread was hijacked.
If you believe information is missing, can you indicate what questions are still left unanswered in your opinion?
With kind regards,
Mike van Riel
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAEJbJphL-sBCStUAwQCWr%2B0dec0gobg0YJm_7rhtmP8mJ6Fw6w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAE%3De0zdt8o81MSdPSTDknXCDbWbg-dCsEzo14uATUKVa18i81Q%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/52CFD4E1.1000605%40gmail.com.