Re: found a bug in 3.13.9 dbLoadTemplate - after all that time

[Ralph Lange <Ralph.Lange@bessy.de>]

>>>>> Bernhard Kuner <Bernhard.Kuner@bessy.de> writes:

  > [...] Why couldn't we have both - as a kind of "value inheritance"?

What about:

 o Allowing $(name=default) in the template database, as the first level
   of default values.
   (-> per template)

 o Allowing a line like
      default{SCAN=Passive, HOPR=9, LOPR=1, ADEL=0.5, MDEL=0.1}
   in the head of a file entry in a substitution file, mutually
   exclusive with the unchanged pattern{} keyword used for tabular
   material - to avoid messy incomprehensive tables.
   The default specifications on this line would override the default
   definitions in the template database.
   (-> per use)

 o Allowing the usual unchanged macro substitutions in the lines of the
   substitution file.
   (-> per instance)

Should fit any of the mentioned cases without implying anything on
anyone, shouldn't it?

Ralph