mramirez schrieb:
> Compiler Design its not a trivial task. IT'S THE DIFFICULT TASK. A
> famous compiler book shows a knight trying to kill a dragon, as a metaphor.
Nobody needs compiler building knowledge to push this matter.
There are other things which prevent package support
- provide an ftp.freepascal.org mirror (requires approx. 1TB/month
traffic) to reduce the matter of download size
- take care of the installer building and provide patches, it takes me
usually several days before a release till the installer works again
because of changed memory locations etc. so we know that we can make a
more complicated build and install process because somebody takes care of it
- make a proposal for a dyn. package naming scheme taking different
OSes, file systems, release and snapshot versions into account.
>
> There is a workaround for this, that is compiling statically Lazarus
> with new units, when a component (package) is added. Is not the perfect
> solution.
>
> But it works.
Actually, I see the delphi solution using dyn. packages as the workaround:
- dyn. packages cause dll hell, keep in mind that _every_ possible
combination of rtl, fcl, lcl needs its own set of dyn. packages
- code in dyn. packages is slower
- even commercial seem not to be able to provide stable debugger support
for dyn. packages
- dyn. packages cause a bigger memory footprint (dyn. packages cannot be
smartlinked)
- dyn. packages multiply download size, we don't ship on CD
The only valid reason for dyn. packages is that someone don't want to
publish its IDE sources
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
