Problem with coupling shared object symbol visibility with protection

[Walter Bright via Digitalmars-d]

On 1/31/2015 11:52 AM, Benjamin Thaut wrote:
> @Walter:
> Making export a attribute seems to be the preferred choice in this discussion.
> Additionaly this was the result of the last discussion around export, a year
> ago, although for different reasons. The last Discussion resulted in DIP 45
> which also proposes making export an attribute. Before I start with the
> implementation, would you be ok with making export an attribute or would you
> veto it?

At this point I suggest simply making those private helper functions public and 
export them. It gets your project moving without waiting for language changes 
(and this is a breaking change).