Re: inlinable functions instead of macros

[Stefan Monnier <monnier@iro.umontreal.ca>]

> problems that make the macros hard to use.  They cannot be invoked
> from GDB, which complicates debugging.  More important, callers

Most of those macros don't need to be used from GDB (e.g. I've never
needed to use ASET from GDB).

> restriction makes callers error-prone.  We've tried to address some of
> the side-effect issues with this hack:

>    /* The IDX==IDX tries to detect when the macro argument is side-effecting.  */
>    #define ASET(ARRAY, IDX, VAL)	\
> 	 (eassert ((IDX) == (IDX)),				\

This should be removed indeed.  I added it temporarily and in any case
it doesn't work (e.g. "i++ == i++" will always return true in my
experience).

> +	Reimplement in terms of eassert_f, blv_found_f, set_blv_found_f.
> +	(eassert_f, blv_found_f, set_blv_found_f): New macros or functions,
> +	containing the guts of the old, but which let the caller specify
> +	file and line number.

I'd rather avoid these kinds of efforts,


        Stefan