[
https://issues.apache.org/jira/browse/SHINDIG-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769892#action_12769892
]
Yuen-Chi Lian commented on SHINDIG-321:
---------------------------------------
I was about to start integrating Shindig into my PHP code and was terrified by
the lack of namespacing (not the PHP 6 'namespace' but the 'conventional'
Namespace_ClassName).
Take a look at Symfony for its sf* namespace, or PHPUnit's and PEAR's rather
verbose Package1_Package2_ClassName approach.
This is something that doesn't really require a long discussion for a decision.
> NameSpace collition in PHP Classes
> ----------------------------------
>
> Key: SHINDIG-321
> URL: https://issues.apache.org/jira/browse/SHINDIG-321
> Project: Shindig
> Issue Type: Improvement
> Components: PHP
> Reporter: bruno rovagnati
> Attachments: namespace_email.patch,
> namespacer_cache_setpref_setprefs.patch, shindig-namespaces.patch,
> shindig_namespace.patch
>
>
> Some classes are having conflicting names such as Cache, Name, Email, Person
> etc... (mainly src/socialdata/opensocial/model/*)
> I suggest to move those class name to a Shindig_Cache, Shindig_Name, etc.
> (Zend-like namespace convention)
> i'll start adding patched to these classes that are conflicting while
> implementing shindig
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
