On 2021-01-01, at 08:22:04, Seymour J Metz wrote: > > I hope that there is at last a warning associated with that, if not an option > for strict enforcement: the most recently active CSECT might not be what was > intended. > > ________________________________________ > From: Jonathan Scott > Sent: Friday, January 1, 2021 10:12 AM > > HLASM was therefore changed again by APAR PH05788 to tolerate > this incorrect usage, in that if CATTR with a given name was > first issued within a DSECT, the definition would be associated > with the most recently active CSECT. > Two wrongs don't make a right. Surely an APAR fix to Metal C could have been produced as promptly as tolerating breakage in HLASM. "Toleration is the mother of mediocrity."
> The Metal C compiler was also changed for APAR PI84091 to avoid > the incorrect usage, although this was no longer necessary with > the HLASM fix. Don't let a product and its documentation become a chaos of toleration fixes. -- gil
