[nem-bug] [Nemerle 0000742]: Strange namespace opening behaviour from within namespace

[feedback at nemerle.org]

A NOTE has been added to this issue.
======================================================================
<http://nemerle.org/bugs/view.php?id=742> 
======================================================================
Reported By:                Snaury
Assigned To:                
======================================================================
Project:                    Nemerle
Issue ID:                   742
Category:                   Compiler
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
======================================================================
Date Submitted:             08-17-2006 07:53 CEST
Last Modified:              08-17-2006 23:12 CEST
======================================================================
Summary:                    Strange namespace opening behaviour from within
namespace
Description: 
Code:

// APPTYPE: dll
namespace Some.Library
{
  using Nemerle.Text;
  using System.Text;
}

// nbuild 1.n
ncc.exe -no-color -t:library -out:1.dll 1.n
1.n:5:3:5:21: warning: N105: namespace `Some.Text' is already open
1.n:5:3:5:21: warning: N105: namespace `Some.Library.Text' is already
open

I'm sure it shouldn't have even tried to open Some.Text and
Some.Library.Text, because I don't say with any using.
======================================================================

----------------------------------------------------------------------
 nazgul - 08-17-06 22:54 
----------------------------------------------------------------------
In Nemerle (and C#) using nested inside namespace XX { }  is opening also
the namespace constructed from enclosing name concatenated to opened one:

namespace A {
  using B;
   // here we have A.B and B opened
}

but here... we clearly see some bug - it should not take Text, only whole
'Nemerle.Text' and 'System.Text' to create additional imports.

----------------------------------------------------------------------
 nazgul - 08-17-06 23:12 
----------------------------------------------------------------------
This is caused by Vlad's change in 6519. I don't really like that change in
API - it is a little bit too breaking, we should have 'EdgeName',
'PartName' or 'NodeName' to access 'name'.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
08-17-06 07:53 Snaury         New Issue                                    
08-17-06 22:54 nazgul         Note Added: 0001426                          
08-17-06 23:12 nazgul         Note Added: 0001427                          
======================================================================