On 21-Nov-2008, at 4:30 PM, Igor Stasenko wrote:
>
> 2008/11/21 Greg A. Woods; Planix, Inc. <woods at planix.ca>:
>>
>> How is another plugin supposed to access this 'bitBlitAtom' handle  
>> that is
>> effectively always in the first plugin's private storage and  
>> literally (as
>> you've declared it above) also in the other plugin module's private  
>> symbol
>> namespace?  (i.e. if it's compiled as a "static" variable in the  
>> first
>> plugin module then there's no way the second plugin can use the  
>> same symbol
>> to refer to the same storage)
>
> Its not in a private storage. When you telling makeAtom(), you
> receiving an atom id for given name which is shared among all plugins.

Perhaps I'm assuming your syntax is literal C code when that is not  
what you meant?

The code you wrote explicitly defines a _static_ (i.e. private) symbol  
for storage that only the one compiled source file will be able to see  
the referenced storage, and only within the scope of the definition.

But I think Andreas Raab hit the nail on the head with his suggested  
ioLoadFunctionFrom() idea.

-- 
					Greg A. Woods; Planix, Inc.
					<woods at planix.ca>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20081124/3d467e1f/PGP.pgp