Re: 18-bugs.patch

[Akim Demaille]

| > Not a good idea if acversion.m4 is read-only but the directory is not.
| 
| Yep.  Besides, the proposed change won't generate acversion.m4 in the
| srcdir.  Is that intended.

Nope, thanks for spotting this.

| Another issue is that, if `sed' doesn't run to completion, for
| whatever reason, you end up with an acversion.m4 whose timestamps is
| newer than its dependencies and that won't be updated on the next
| `make'.  That's the reason for using the temporary file.

Yep, I know, but in this case, it looked overkill to me.  But I agree,
I must have had some slight absence yesterday, it's a stupid change.

| I also recommend to use mv, and only fallback to cp and rm if mv
| fails.
| 
| >> +* Grave bugs
| 
| I'd say `serious' instead.  Even though grave is a synonym with it,
| ``grave bugs'' admits other readings that sound odd, or even funny.
| Or maybe you really meant insects that inhabit coffins? :-)

:) :) :)

| >> +** : ${foo=$val}
| >> +There are problems on Ultrix and I don't recall which architecture.
| 
| There's also the problem of having cached variables containing the `}'
| character, that breaks with Solaris' /bin/sh.  I don't know whether
| this is a ``grave bug'', though :-)

About this bug, does it happen whenever there is a non balanced `}',
or as soon as a `}' is found?