[fpc-devel] Dotted namespace

Sven Barth pascaldragon at googlemail.com
Wed Jan 27 17:26:44 CET 2016


Am 27.01.2016 16:31 schrieb "Dmitry Boyarintsev" <skalogryz.lists at gmail.com
>:
>
> On Wed, Jan 27, 2016 at 8:46 AM, Maciej Izak <hnb.code at gmail.com> wrote:
>>
>> 2016-01-27 14:44 GMT+01:00 Michael Van Canneyt <michael at freepascal.org>:
>>>
>>> On Wed, 27 Jan 2016, Juha Manninen wrote:
>>>
>>>> Hey guys ...
>>>>
>>>> Now this Generics.Collections is completely hijacked by a namespace
>>>> discussion. Does it mean the original issue is again buried and
>>>> forgotten for another year or two?
>>>
>>>
>>> No. Sven is on it.
>>
>>
>> Anyway new thread for "Dotted namespace" is good idea :P
>
>
> "Dotted namespace" how's that?
> shouldn't be rather be "Dotted unit names" and "namespaces"?
> Since "dotted name" actually specify "namespace".
> And a name of a space (scope), shouldn't have any dots  since dot is a
separator.
>
> Because "dotted unit names" (without actual namespaces) might break
compatibility with delphi's namespaces.
>
> See:
http://docs.embarcadero.com/products/rad_studio/delphiAndcpp2009/HelpUpdate2/EN/html/devcommon/usingnamespaces_xml.html
>
> For example: section "Multi-unit Namespaces"
> unit MyCompany.ProjectX.ProgramY.Unit1
> unit MyCompany.ProjectX.ProgramY.Unit2
>
> "In this example, the namespace MyCompany.ProjectX.ProgramY logically
contains all of the interface symbols from unit1.pas and unit2.pas.
>
> Symbol names in a namespace must be unique, across all units in the
namespace. In the example above, it is an error for Unit1 and Unit2 to both
define a global interface symbol named mySymbol. "

We're talking about one and the same feature. FPC's dotted unit names are
implemented based on Delphi's namespace feature, but since they aren't
namespaces in the strict sense we prefer to use the more accurate name of
"dotted unit names".

Regards,
Sven
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20160127/ae04aca0/attachment.html>


More information about the fpc-devel mailing list