Re: [Pyobjc-dev] GNUstep.

[Ronald O. <ous...@ci...>]

On Saturday, Jan 4, 2003, at 17:12 Europe/Amsterdam, Jack Jansen wrote:

>
> On zaterdag, jan 4, 2003, at 13:42 Europe/Amsterdam, Ronald Oussoren 
> wrote:
>
>>
>> On Saturday, Jan 4, 2003, at 10:42 Europe/Amsterdam, Mirko Viviani 
>> wrote:
>>
>>> Ciao!
>>>
>>> I'm trying to get pyobjc working on gnustep... I don't know the 
>>> pyobjc internals
>>> yet but should it be possible to rename objc_error to something else 
>>> ?
>> Sure, especially given the name-clash your having. I've renamed 
>> objc_error to ObjCExc_error.
>
> Why not make all externally visible symbols (at the C level, I'm not 
> talking about Python here) start with "pyobjc_" or some such?

We currently use 'OC_' as the prefix on Objective-C class names (such 
as OC_PythonArray) and ObjC as the prefix on most newer C code 
(objc_error was one of the exceptions). Older code uses no prefix or 
'objc_' as the prefix.

I agree that it would be wise to use a prefix on all externally visible 
symbols. We could use either 'OC', 'ObjC' or 'PyObjC', with mixed case 
identifiers. Now that I've put some more thought in it I think that 
PyObjC would be the best choice because it is highly unlike that anyone 
else uses this prefix. I initialy choose ObjC because it was already in 
use (ObjCPointer is a surviving example of this) and because the 'Py' 
prefix is claimed by Python.

Summary of my proposal: Use the same naming scheme as the Python core, 
but using 'PyObjC' instead of 'Py' (see also PEP 7 at 
http://www.python.org/peps/pep-0007.html)

I'll write a coding style document for PyObjC that mentions this. If 
everyone agrees we can then rename all externally visible symbols, 
preferably only once.

Ronald