Eric Blake <ebb9 <at> byu.net> writes: > +AT_SETUP([AS@&t <at> _INIT_GENERATED]) > + > +AT_DATA_M4SH([script.as], [[dnl > +m4_define([AS_MESSAGE_FD], [1])
By the way, this test points out another m4sh flaw that needs fixing - we should consider providing default values for AS_MESSAGE_FD (1) and AS_MESSAGE_LOG_FD (empty), which can be changed by clients, so that AS_MESSAGE works if the client doesn't touch these macros. The manual documents that they exist, but is silent on whether the users may/must redefine them (and AS_INIT_GENERATED currently doesn't work if the user does not redefine them). Also, if AS_MESSAGE_FD is 1, AS_INIT_GENERATED currently produces a line exec 1>&1 I'm not sure if that is a no-op on all shells, or whether it needs m4 logic to avoid that line when AS_MESSAGE_FD is not set somewhere besides stdout. -- Eric Blake
