[fpc-devel] Pascal Standard, and what we can do.

Sven Barth pascaldragon at googlemail.com
Mon Jul 20 11:21:37 CEST 2015

Am 20.07.2015 09:21 schrieb "Marco van de Voort" <marcov at stack.nl>:
> In our previous episode, Sven Barth said:
> > The way we write software evolves however. Things that were thought as
> > state of the art 25 years ago aren't necessarily nowadays (for example
> > procedural programming that has been mostly superseded by object
> > programming). And in this regards programming languages are like natural
> > languages: they evolve, they change. If a language doesn't evolve
> > it can be considered dead (e.g. Latin, Ancient Greek).
> > So I personally support the addition of new features to FPC as long as
> > don't interfere with backwards compatibility and fit into the language
as a
> > whole.
> The question though if a few haphazardly copied features make a 20+ year
> project suddenly state of the art. Some of the "old" stuff goes deep.

Of course. But there aren't only "20+ year old project[s]". While it might
be not always worthwhile to use new features in an old project they can
nevertheless be useful when you're working on a new project from the ground

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20150720/162b8b9e/attachment.html>

More information about the fpc-devel mailing list