Sharing in D

BCS ao at pathlink.com
Fri Aug 1 12:41:38 PDT 2008


Reply to Steven,

> I have no idea what the middle ground is :)  I'm just saying that
> without that middle ground, it's going to feel like I'm writing code
> specifically for sharing or not sharing,

I stand corrected the middle ground is "don't let me do anything where it 
matters" No cocreate thing would take on this attribute but references with 
it could be made from either side.

> and the shared keyword loses
> a lot of its meaning as a general type modifier.  I can't just slap a
> shared label on anything because that object needs to be specifically
> written to be a shared object.
> 
> And in the case of functions which take those objects or data types as
> parameters, slapping a shared label on something means I have to use a
> completely different set of functions, which might not exist.  If I
> have to use a library for some reason or another, I might just be
> tempted to cast away the shared.  I might have no other choice.
> 
> -Steve
> 





More information about the Digitalmars-d mailing list