Date: Wed, 26 Jun 2002 16:39:08 +0100 From: Laurynas Biveinis X-Mailer: The Bat! (v1.60h) Personal X-Priority: 3 (Normal) Message-ID: <114252854175.20020626163908@softhome.net> To: sandmann AT clio DOT rice DOT edu (Charles Sandmann) CC: djgpp-workers AT delorie DOT com Subject: Re: Clio 2.04 packages In-Reply-To: <10206151751.AA18505@clio.rice.edu> References: <10206151751 DOT AA18505 AT clio DOT rice DOT edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 Jun 2002 14:40:16.0613 (UTC) FILETIME=[63401150:01C21D1F] 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 My university exams have taken all my time in past few weeks, and now I'm making my ways through e-mail backlog (slowly). I'm sorry if I tell what others have already said, but anyways: > (I wasn't around during the development, and haven't read the back > discussions on this, so forgive me if this has all been covered... > Why wasn't something like windows .lnk format chosen? I've looked into this and discussed in this list. I don't remember the exact outcome, but there are several problems: since symlink file won't have any standard extension like .lnk, it would be impossible to tell if a file is a symlink without opening it - a quite slow operation. Current symlink implementation checks file size first (it should be 510 bytes), it catches 99% of non symlink files. > Why remove the > old EXE stubing type symlink - how to run these from command prompt? I was thinking about creating new utility 'linkexe' which would be based on code from pre-symlink symlink() implementation. Sadly, I never got around implementing this. > Some sort of documentation on symlinks?) I was thinking about that too. However, I was very unsure about what should I document. I was using Single UNIX Specification v2 for API reference, so documenting that didn't seem necessarry. File format is very simple and obvious. Maybe I should document which functions support symlinks, which do not, and why?.. Maybe actual symlink resolution algorithm?.. > Why? Because of non-DJGPP tool chain support I would suspect we would > want to minimize symlink use to portability/testing support. Sorry I don't understand. Could you be more specific please? Laurynas