"Skybuck Flying" <Window...@DreamPC2006.com> wrote:
> It probably started with some *.CFG or something... are these *.CFG
> even used anymore ?
>
> Doesn't seem like it ?!? Could be wrong though ! ;)
Yes, I think CFG start it all first. But if you think about where it came
from... it was because the compiler is made configurable in the first
place. Don't know since when, but my first Pascal compiler was Turbo
Pascal 4 (TP4 for DOS), and its compiler is already configurable. I
didn't have the chance to know more about earlier versions, but from
computer magazines years back, TP3 compiler is already configurable too.
...Crap. This makes me want to hunt them.
Apparently, CFG is still used as a backup when DOF/XML is missing.
DOF/XML is basically a CFG plus bells & whistles settings for the IDE.
CFG holds only the relevant settings for project compilation. Loosing all
three files above can make a program broken after compilation, or even
not compilable at all. Due to e.g.: record alignment, optimization,
runtime checkings, etc.
> DFM is not so bad, but that's how it slowly sneaks in... DFM first,
> XML later.
Yes, I notice DFM is slowly extended on some Delphi versions. It may be
changed to XML later, but DFM is pretty much like Microsoft RC files
where it's still used even now - at least for non .NET programs (.NET is
crap, BTW). Like RC files, DFM is part of the actual program itself. It's
unlikely be easy to phase out. Heck... take a look at bitmap format, it's
been there since Windows 2 or even the first Windows, and it's still used
by the latest state of the art, Windows 8 kernel (Windows 8 is crap too).
Even with all these migration to DOF and XML, Delphi is still doing it
carefully - taking it easy for programmers. Compare it with Visual
Studio, where almost every version, the project configuration format
changes. Now that, is one heck of a crap.