OK, I'm trying to convince myself that unqualified (shortened) names would be OK after USING statement as a feature. While we do follow c++ naming rules for external linkage (ABI), the namespace/using concept is within the compiler only, so we don't necessarily have to copy c++ in every respect.fxm wrote:But that works for a non-member procedure declared in a Namespace but outside implemented through a 'Using namespace_name':coderJeff wrote:This seems like it should be the normal behaviour and correct that the definition should be fully qualified, either inside a namespace block, or with the namespace identifier prefix
Here we should probably get an ambiguous symbol definition, as we don't reliably know if we are defining P() or N.P():
Code: Select all
declare sub P()
namespace N
declare sub P()
end namespace
using N
sub P()
end sub