[asdf-devel] source file encoding

[Faré]

On Fri, Apr 13, 2012 at 15:36, Pascal Costanza <pc at p-cos.net> wrote:
> I agree. Encoding is a per-file property, not a per-system property. If it is defined per system, then maintaining the information also becomes an overhead.
>
As for many other things (the :around-compile hook, for instance),
ASDF allows you to specify inherited per-system or per-module defaults
that can be overridden in individual file components.

> For example, I have source files that are shared by different system definitions.
> If I would now want to change the encoding of that file,
> I would also have to update the system definition(s) that it is part of.
> I don't think that's a good idea.
>
Tough for you, but a very little inconvenience, and
not a violation of ASDF 2's design principle for configuration:
the same people who decide and know are those who specify the information.

How often do you not only share a source file between multiple systems
(usually a bad idea, because of how caching and change detection works),
but also change its encoding?

PS: did you try the latest ASDF, with logical-pathname fixes just for you?

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
The uploaded man cut himself from the world. The optimizer saw the simulation
would have no more side-effects and optimized it all away.