Date: Thu, 11 May 2000 10:31:04 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: Wes Peters <wes@softweyr.com> Cc: John Baldwin <jhb@FreeBSD.org>, arch@FreeBSD.org, Peter Wemm <peter@netplex.com.au> Subject: Re: .s -> .S filename change in /sys Message-ID: <20000511103104.A5531@dragon.nuxi.com> In-Reply-To: <391A525F.E4B9D3DA@softweyr.com>; from wes@softweyr.com on Thu, May 11, 2000 at 12:25:35AM -0600 References: <200005102341.TAA07315@server.baldwin.cx> <391A525F.E4B9D3DA@softweyr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 11, 2000 at 12:25:35AM -0600, Wes Peters wrote: > Ick. Someone else pointed that out, too. The command above at least > gives you a 61-file starting place, rather than the entire system. > OTOH, Peter's point about renaming all the .s files, except those it > would actively hurt, makes more sense. Only those that should be ".S" files should be renamed. > I'd even vote for changing the comments on the few in /sys/boot and > renaming them as well. Then I'd vote for making all our ".c" files to use C++ comments and rename them to ".C". That would make as much sense. We've been mis-naming some of our ASM files. I am trying to change that. The files should be named properly. If they need to be run thru the C pre-processor/cc then they should be .S files. If not, they should be named .s files. I don't care if some can't keep the extention straight. How do people keep straight .c and .C then? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000511103104.A5531>