[lazarus] circular unit reference

Mattias Gaertner nc-gaertnma at netcologne.de
Sat Nov 15 08:17:40 EST 2003


On Sat, 15 Nov 2003 14:10:22 +0100
rstar at mnet-online.de wrote:

> Florian Klaempfl wrote:
> 
> > Andreas Hausladen wrote:
> > 
> >>> Simply delete messages.pp for win32.
> >>
> >>
> >>
> >> Yes, this would be the easiest way for a LCL developer but it is no 
> >> real solution. Or would you say to a customer: "Please delete a
> >> file for a successful compilation" ? And what is if the the developer 
> >> wants to migrate to Linux? "With" the deleted file he must
> >> download the LCL again if he has not backuped the file.
> >> I think the solution I've chosen for the Delphi port is better than 
> >> deleting a file.
> > 
> > 
> > No. The final solution is to move the messages.pp to the lcl/nonwin32 
> > dir, however the lazarus developers didn't do this yet.
> > 
> > _________________________________________________________________
> >     To unsubscribe: mail lazarus-request at miraclec.com with
> >                "unsubscribe" as the Subject
> >   archives at http://www.lazarus.freepascal.org/mailarchives
> > 
> 
> The current thread shows that there a always problems with
> includes, paths, circular refereces etc.
> 
> One of these guidelines might be helpful:
> 
> - Don't use includes (all in one file); example: CLX from Borland

There are no problems with such includes.


> - Use #ifdef "target" for platform specific things

Only readable for 2 targets.


> - One person is responsible for a file
>    (it seems that the lcl stuff is managed by different persons)

we have no full time employees and no one knows everything.


> - Use .pas extension only

That can be done. Although it's only important for FPC to Delphi porting,
while Lazarus is quite the opposite direction.


Mattias






More information about the Lazarus mailing list