On 30-Sep-07, at 2:08 PM, Joe Huber wrote:
> If I call a method in a module using it's qualified name, and that
> method does not exist, is it an error for the compiler to use a
> global name instead? I would expect a compile time error, but I'm not
> fully conversant with the new Namespace capability, so maybe it's
> somehow a feature???
>
> If I call ModuleName.MethodName, and MethodName doesn't exist in that
> module, RB2007r4 uses a global constant I have called MethodName
> instead.
>
>
> Since it didn't find the method within the the specified module, I
> would have expected a compile time error. Or am I misunderstanding
> why this might be a desired namespace feature?
Sounds like this verified bug <http://www.realsoftware.com/feedback/
viewreport.php?reportid=gzvtteul>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|