Guenter Milde wrote: > Thinking about it while writing aastex6.layout, there is a major > disadvantage of the "old loads new" approach: > > * aastex6.layout inputs aastex.layout and currently only changes the name > and referenced LaTeX class file. > > I future, it should also support commands new in aastex v. 6. > > Adding new styles to aastex6.layout is simple and does not require any > changes to the old aastex.layout. > > OTOH, if the old aastex.layout would input the new aastex6.layout, any > adding of a new style there would require a new "NoStyle" in the old > layout. > > > Generally, as the old layout is stable but the new a "moving target", the > method "new loads old" is preferable, as this allows to keep "old" at the > proven status. (This is als important, because we usually do not test with > obsolete LaTeX classes/packages.)
Very good point. For me personally this is the killer argument for always doing "new loads old". Georg
