On Thu, Aug 25, 2011 at 05:03:23PM +0200, [email protected] wrote: > That's a canned recipe, and as mentioned in my first message: not > elegant, but working ;-)
I wasn't sure about "canned recipe". Define elegant. ;-) (1) Using pattern rules allows one to compress recipes. Things that don't fit into the pattern will have to get a rule of their own. General software design pattern: generalisation + special cases (2) If the generation for both general and special cases is going according to the same recipe, it should be defined in one place. General software design pattern: single place of authority If you don't care about compression, you can expand the rules for all known targets using the technique Lane's mentioned, lose (1) but keep (2). If you were to keep (1) and (2) and use Lane's solution, you will end up with a canned recipe somewhere.
signature.asc
Description: Digital signature
_______________________________________________ Help-make mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-make
