On Fri, 12 Feb 2010, Will Coleda wrote:
> What about this for a more clever @@ replacement syntax? then we can
> setup something complicated per-file but have a sane default.
>
> --
>
> Takes the specified source file, replacing entries like C<@key@> with
> C<key>'s value from the configuration system's data, and writes the results
> to specified target file.
>
> If a C<?> is present in the C<@key@>, the replaced value will first
> try touse the full key, but if that is not present, the key up to the
> C<?> is used.
> For example, if C<@cc_warnings?src/embed.c@> is used, and that key doesn't
> exist, the fallback key would be C<@cc_warnings@>.
I think that could work. My initial inclination would have been to use an
existing syntax, perhaps something like C<$cc_warnings{'src/embed.c'}>,
instead of inventing a new syntax, but it doesn't really matter very much.
He who implements it gets to choose. The main thing is it should
ultimately be easy for a porter to add a specific case to a hints file
that will then get used up by the general config mechanism.
I'm afraid that I'm unlikely to have any opportunity to do anything useful
with this for quite a while, so go with whatever makes sense to you.
--
Andy Dougherty [email protected]
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
