[Lazarus] Support for dotted unit name

Hans-Peter Diettrich DrDiettrich1 at aol.com
Fri Nov 4 15:51:40 CET 2011

Sven Barth schrieb:
> Am 04.11.2011 13:08, schrieb Hans-Peter Diettrich:
>> Sven Barth schrieb:
>>> I don't think that Embarcadero considers dotted unit names as a relict
>>> as they've improved the concept with a "default namespace" in XE2 (I
>>> don't know whether I personally consider that as a improvement though
>>> ^^) and also introduced dotted names for all RTL, VCL and FireMonkey
>>> units.
>> Well, so what's the role of "Delphi" at all? What remains is an IDE and
>> a compiler, with various GUI extensions. Will Lazarus follow this route
>> - should it ever???
> Well, Lazarus IS basically an IDE with various GUI extensions.

Lazarus only supports one GUI: LCL. Adding fpGui shows part of the 
problems, which will occur with a very different GUI API, like FireMonkey.

> The 
> dotted name space feature is provided by the compiler which is in our 
> case FPC (or did I miss something that we now call the compiler Lazarus 
> as well :P )

The new strings also are an FPC issue, which may require a different 
LCL. IMO it's not a good idea to mix new Delphi features with attempts 
to provide a single development environment.

>> We have enough problems in implementing a VCL compatible LCL, with
>> attempts to make it compatible with various widgetsets, and with new
>> Delphi versions. All this could be trashed in an attempt to add
>> FireMonkey compatibility. It would be better to start a very new project
>> for that purpose, whose IDE could be based on the LCL, like the Delphi
>> IDE is based on .NET since D20xx.
> In the end we might not need to add FireMonkey compatibilty completely 
> by ourselves, as FireMonkey is already FPC compatible (Embarcadero uses 
> FPC for iOS!).

Embarcadero could not provide designers for FireMonkey right now, and 
Lazarus will run into the same problem - as can be seen with the fpGui 
widgetset (which is more LCL compatible than FireMonkey or KsDev). 
Embarcadero failed with a VCL.NET, now they even don't try to provide a 
VCL.FireMonkey. Lazarus is even more problematic, since it cannot load a 
different component library dynamically, instead it must be rebuilt for 
a different FMCL.


More information about the Lazarus mailing list