Message-ID: <3957BF10.7EBB2B8D@softhome.net> Date: Mon, 26 Jun 2000 22:37:36 +0200 From: Laurynas Biveinis X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: lt,en MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: Patch: chown() preparation for symlinks References: <395643BB DOT 7109B0DA AT softhome DOT net> <200006261453 DOT KAA11494 AT envy DOT delorie DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com DJ Delorie wrote: > > > -#include > > This include is *never* redundant. Without this, we will create a > libc that violates ANSI/POSIX namespace rules. Please do not remove > includes just because it "compiles anyway" without them. They're > there for a reason. Yes; I knew that libc/stubs.h is special. So I looked there at first, and I haven't found any #define chown __chown, neither there was any function (in fact, single __file_exists) referenced. So I assumed that removing it was safe. Is this assumption wrong? Or is it general policy to #include everywhere in libc sources to play safe? Laurynas