[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: expand-file-name in fileio.c twice?
From: |
Richard Stallman |
Subject: |
Re: expand-file-name in fileio.c twice? |
Date: |
Mon, 22 Oct 2001 07:44:42 -0600 (MDT) |
Some of the #if 0'ed functions give a doc string because it's too long
for some preprocessors.
That is true.
Now that we are using comment syntax for the doc string,
we can put those long doc strings into the real function definition.
I'd say it's probably OK to remove all the #if 0'd duplicate DEFUNS now.
Yes, after moving the doc strings, if they do not contain any real code.
(The ones that were made to hold doc strings do not contain code.)
- Re: expand-file-name in fileio.c twice?, (continued)
- Re: expand-file-name in fileio.c twice?, Miles Bader, 2001/10/21
- Re: expand-file-name in fileio.c twice?, Pavel Janík, 2001/10/21
- Re: expand-file-name in fileio.c twice?, Richard Stallman, 2001/10/22
- Re: expand-file-name in fileio.c twice?, Eli Zaretskii, 2001/10/22
- Re: expand-file-name in fileio.c twice?, Richard Stallman, 2001/10/24
- Re: expand-file-name in fileio.c twice?, Eli Zaretskii, 2001/10/25
Re: expand-file-name in fileio.c twice?,
Richard Stallman <=