Re: Portable API for writing own macros

[Raja R Harinath]

Akim Demaille <address@hidden> writes:
>>>>>> "Andrej" == Andrej Borsenkow <address@hidden> writes:
>Andrej> Sometimes just the "official" macros, like AC_TRY_COMPILE etc
>Andrej> are not enough. 2.50 includes many very insteresting macros
>Andrej> (AC_VAR_PUSHDEF/POPDEF, AC_*_IFELSE, m4_* suite to name
>Andrej> some). What macros can be "safel" used to write own macros
>Andrej> (safely meaning they remain in future versions)?
> 
> I don't expect these macros to change, but I won't document them and
[snip],
>  they can change.
> 
> But again, I don't think they will.  
> 
> So use them.

Well, AC_VAR_* were recently renamed to AS_VAR_* (if that's considered
a change :-)

- Hari
-- 
Raja R Harinath ------------------------------ address@hidden
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash