Re: 'database' expands to something else

[Eric Blake]

On 06/01/2010 04:02 PM, Brent Gulanowski wrote:
> version 1.4.6 (sorry)

You may want to consider upgrading; that is several years old, and has
several bugs fixed in the meantime.  The latest is 1.4.14.

> 
> On 2010-06-01, at 6:02 PM, Brent Gulanowski wrote:
> 
>> I can't find any reference to a macro named "database", but if I use that 
>> word in my m4 script, it gets expanded to usually the value of the last 
>> argument provided to previous macro. It's quite frustrating, since I need to 
>> use the word "database" for other things.
>>
>> The word "database" isn't found anywhere on the m4 site, according to 
>> Google, so I'm not really sure what's going on.

You are correct that database is not a builtin m4 macro.  Most likely,
you are inadvertently defining it as a macro somewhere in your m4 file,
perhaps due to insufficient quoting of macro arguments.  But without
seeing your input m4 file, my guess is as good as yours.  If you can
post a simple testcase, then we can help you debug it.  Meanwhile, you
may want to try:

m4 --debug=aeq --trace=database --trace=define

to see if that helps you spot where you (accidentally) defined database
as a macro name.

-- 
Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

signature.asc
Description: OpenPGP digital signature