• H. S. Teoh (9/9) Sep 05 2013 Today, I was surprised to discover that std.regex has a public stack
• Vladimir Panteleev (8/15) Sep 05 2013 The declaration is not public - there is a "private:" line at the
• Dmitry Olshansky (7/18) Sep 06 2013 LOL I couldn't stress the importance of that bug better :)
• Gary Willoughby (3/5) Sep 06 2013 Wow! O_o
• eles (3/6) Sep 06 2013 Yes. The compiler has been progressing since '99. O_o

"H. S. Teoh" <hsteoh quickfur.ath.cx> writes:

Today, I was surprised to discover that std.regex has a public stack
implementation (std.regex.Stack). Is this intended to be public? It's
causing a conflict with my code, and I found it strange that importing
std.regex should declare a type called 'Stack'.

I'm refraining from filing a bug for now, just in case there's a good
reason for this that I didn't think of.


T

-- 
Without outlines, life would be pointless.

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Thursday, 5 September 2013 at 22:49:49 UTC, H. S. Teoh wrote:
 Today, I was surprised to discover that std.regex has a public 
 stack
 implementation (std.regex.Stack). Is this intended to be 
 public? It's
 causing a conflict with my code, and I found it strange that 
 importing
 std.regex should declare a type called 'Stack'.

The declaration is not public - there is a "private:" line at the 
top of the file, and the module declares its public symbols 
explicitly.

Conflicts between public and private symbols is a long-standing 
problem of D:

http://d.puremagic.com/issues/show_bug.cgi?id=1238
http://wiki.dlang.org/DIP22

Dmitry Olshansky <dmitry.olsh gmail.com> writes:

06-Sep-2013 03:11, Vladimir Panteleev пишет:
 On Thursday, 5 September 2013 at 22:49:49 UTC, H. S. Teoh wrote:
 Today, I was surprised to discover that std.regex has a public stack
 implementation (std.regex.Stack). Is this intended to be public? It's
 causing a conflict with my code, and I found it strange that importing
 std.regex should declare a type called 'Stack'.

 The declaration is not public - there is a "private:" line at the top of
 the file, and the module declares its public symbols explicitly.

 Conflicts between public and private symbols is a long-standing problem
 of D:

 http://d.puremagic.com/issues/show_bug.cgi?id=1238
 http://wiki.dlang.org/DIP22

LOL I couldn't stress the importance of that bug better :)
Time to make private symbols invisible outside!
(isn't that what module-level encapsulation was all about)

https://github.com/D-Programming-Language/dmd/pull/739

-- 
Dmitry Olshansky

"Gary Willoughby" <dev nomad.so> writes:

On Thursday, 5 September 2013 at 23:11:21 UTC, Vladimir Panteleev 
wrote:
 Conflicts between public and private symbols is a long-standing 
 problem of D:

Wow! O_o

"eles" <eles eles.com> writes:

On Friday, 6 September 2013 at 18:16:18 UTC, Gary Willoughby 
wrote:
 On Thursday, 5 September 2013 at 23:11:21 UTC, Vladimir 
 Panteleev wrote:
 Wow! O_o

Yes. The compiler has been progressing since '99. O_o