From: sandmann AT clio DOT rice DOT edu (Charles Sandmann) Message-Id: <10302111457.AA01750@clio.rice.edu> Subject: Re: fix for copyrite.c[c]/copyrite.pl To: cyp AT fb14 DOT uni-mainz DOT de (Cyrus Patel) Date: Tue, 11 Feb 2003 08:57:40 -0600 (CST) Cc: djgpp-workers AT delorie DOT com (DJGPP developers) In-Reply-To: <3E48E5B7.27234.C850F28B@localhost> from "Cyrus Patel" at Feb 11, 2003 11:58:25 AM X-Mailer: ELM [version 2.5 PL2] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > btw, in an NT (2K) VDM however I saw 'file not found' errors for > stat() when the pathlen > 64. Shouldn't LFNizing have avoided that? No, LFN on W2K/XP still have path length limits on the short name equivalents. It shows how it works under the hood ... There is code in DJGPP to work with this - but you must use relative paths instead of absolute paths when deep in the directory structure. > > I should clarify - the original program had main(void) - so had no > > options - and always behaved a particular way. The new version takes > > arguments. [Documentation] > > Yes, but it behaves the same way as the old .cc if no arguments are > provided. ie, specifying which directory to start in is optional. But if you add new features you must document them... Suppose someone was calling the old program incorrectly with a command argument which was ignored. New one behaves differently. So back to main(void) - or write usage documentation. If a new feature is worth adding it's worth documenting. > * - If the file contains a non-DJ copyright *AND* a DJ copyright > * *AND* that DJ copyright was an automatically prepended one, > * then remove the latter - It had been prepended by the old > * broken copyright.cc. This functionality is a by-product > of the "find copyright" process, and is a one-time fix. I think the last block should be handled by manual edits, especially since it may have modifications copyright DJGPP. There probably should be a slightly different header to show this.