mcpp seems to canonicalise all whitespace to TOK_SEP.  The code in
expand.c for dealing with TOK_SEP writes out a space, unless the
previous character was also TOK_SEP.  This means that:
'#define foo bar\n'
will expand to:
'TOK_SEP#defineTOK_SEPfooTOK_SEPbarTOK_SEP'
so, a line containing only 'foo', gets converted to 'bar ', because
the \n is also treated as TOK_SEP.

This breaks things very badly when xrdb uses mcpp; resources change
from 'Foo.bar:\t#123456\nBar.baz:\t#654321\n', to
'Foo.bar:\t#123456 \nBar.baz:\t#654321 \n' (note the extra spaces).
X colour lookups then fail, because it doesn't strip spaces.

The way I 'fixed' this in Ubuntu was to just always skip TOK_SEP, but
this means that:
'#define foo bar \n'
will expand 'foo' to 'bar', instead of to 'bar '.  I don't know if this
behaviour is either desired or correct, however.  So, if always calling
continue in the TOK_SEP case in expand.c is incorrect, then mcpp needs
to differentiate general whitespace from newlines.

Cheers,
Daniel

tags 339683 + patch
kthxbye

So it turns out that cpp also skips trailing whitespace:
'#define FOO bar \n'
turns 'FOO' into 'bar' with the cpp from gcc.  So I'd say that if it's
not *correct* behaviour (which it almost certainly is), then it's
probably expected. ;)

I've also attached a patch which implements this, and works.

Cheers,
Daniel

forwarded 339683 kmatsui@t3.rim.or.jp
thanks

After packaging new release of 2.6.1, I have checked
that this bug has not yet been fixed.  So, I have
forwarded this bug report again, this time in Japanese
(my translation).  Hopefully, it will be fixed soon.

tag 339683 + wontfix
thanks

The upstream auther said, it's not a bug, but a feature.
For use of xrdb, he recommended use of -@old option.

Control: tags 339683 - patch

Untagging patch, thus.