[fpc-devel]Message *bounced*

O/T-Track+ 2.66b "O/T-Track+=202.66b" at f854.n292.z2.fidonet.org
Wed Sep 6 07:58:42 CEST 2000

*      The e-mail-message appended below is list- or mailserver-related
*   That type of mail will by definition not be processed on this system
*         and in general is not accepted in the fidonet.org-domain.
*      To avoid these bouncings the listkeeper is kindly requested to
*   remove any subscription coming from a z2.fidonet.org-style address.
*    If you have reason to believe your message was removed without due
*     reason then kindly inform 'postmaster at f854.n292.z2.fidonet.org'.

    From:  Marco van de Voort @2:292/862
    To:    fpc-develop @2:5020/1305.201
    Subj.: Re: [fpc-devel]TP compatible fsplit()
    Dated: 05 Sep 00  10:46:14
    [processed here:  06 Sep 00 09:58:42]

@TOPT 201
@INTL 2:5020/1305 2:292/862
@MSGID: snail.stack.nl dfc23483
@REPLY: laptop 74461b4d
@REPLYADDR: fpc-devel at lists.freepascal.org
@REPLYTO: 2:292/862 at fidonet UUCP
@PID: ELM [version 2.4ME+ PL60 (25)]
@RFC-Received: from vekoll.saturnus.vein.hu (root at vekoll.saturnus.vein.hu
[]) 	by infomag.iguana.be (8.9.3/8.9.3) with ESMTP id UAA16395 	for
<fpc-develop at p201.f1305.n5020.z2.fidonet.org>; Tue, 5 Sep 2000 20:47:13 +0200
@RFC-Received: from vekoll.saturnus.vein.hu (daemon at localhost []) 	by
vekoll.saturnus.vein.hu (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id KAA25190;
	Tue, 5 Sep 2000 10:46:22 +0200
@RFC-Received: from mailhost.stack.nl (vaak.stack.nl []) 	by
vekoll.saturnus.vein.hu (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id KAA25175
	for <fpc-devel at lists.freepascal.org>; Tue, 5 Sep 2000 10:46:19 +0200
@RFC-X-Authentication-Warning: vekoll.saturnus.vein.hu: Host vaak.stack.nl
[] claimed to be mailhost.stack.nl
@RFC-Received: from snail.stack.nl (snail.ipv6.stack.nl
[3ffe:604:3:9:4a54:e8ff:fe29:b98c]) 	by mailhost.stack.nl (Postfix) with ESMTP
id 67EA814E46 	for <fpc-devel at lists.freepascal.org>; Tue,  5 Sep 2000 10:46:18
+0200 (CEST)
@RFC-Received: by snail.stack.nl (Postfix, from userid 816) 	id AD948C63; Tue, 
5 Sep 2000 10:46:14 +0200 (CEST)
@RFC-In-Reply-To: <000401c01712$cf925da0$0600a8c0 at laptop> from Thomas Schatzl
at "Sep  5, 2000 09:31:42 am"
@RFC-Message-Id: <20000905084614.AD948C63 at snail.stack.nl>
@RFC-Sender: fpc-devel-admin at lists.freepascal.org
@RFC-Errors-To: fpc-devel-admin at lists.freepascal.org
@RFC-X-Mailman-Version: 1.0rc2
@RFC-List-Id: FPC developers' list <fpc-devel.lists.freepascal.org>
@RFC-X-BeenThere: fpc-devel at lists.freepascal.org
To: fpc-devel at lists.freepascal.org
From: marcov at stack.nl (Marco van de Voort)
Reply-To: fpc-devel at lists.freepascal.org

> such
> > > a name) it produces garbage. It's the 'compatiblest' way I found, at
> least
> > > Lee John's recursive directory search works then with LFN too.
> >
> > Why that? If some idiot calls a file "readme..txt" and you try to get
> > the extension, you get ".txt", and conclude you can't open it with
> > notepad?
> You get '..txt' in this case. The extension is always including the point.
> Btw, Windows accepts a file with '..txt' being a '.txt' file. (e.g. it uses
> a routine to detect extensions similar to your old routine)

Then maybe we should create such a routine in the rtl. SHould be easy.
> > The points remain a problem. Both if you stick them with the name or
> > the extension (and can't leave them out, because you can't
> > concatenate it back together again)
> >
> > Marco van de Voort (MarcoV at Stack.nl or marco at freepascal.org)
> But consider the directory '..' (previous directory) ! TP puts everything
> after the first dot into the extension (e.g both dots). This is usually
> checked for in directory traversals, because both this one and '.' have to
> be ignored (the exit clause in the recursive call).

Less important for compability reasons. You usually use fsplit to find paths
(and then discard the filename etc parts), or split the filename into
filename and extension.

> Else you get a dot in the name and a dot in the extension and checks fail
> resulting in an endless loop until the stack overflows. 

Seems through, but I don't see this actually happen. While the other might
break code.

(btw, actually FPC
> should issue an RTE but not crash back to Windows when compiled as a GO32V2
> program; same for the Win32 compiled program)

You mean when the stack overflows?
> Exactly this is the problem. Not a person creating weird file names.
> I already said that I don't really like it (because it's not the way OSes
> handle this too).
> TP rtl is aching everywhere, don't tell me.
> You could add a simple check for '..' too overriding the whole other split
> function - but that's even more a hack.
> This solution is best imho.
> Or do you have a better idea ? See his code and try. (I am not an expert in
> dir traversals, I just made it to work - but I think the checks done are
> correct)

I don't think the ".." directory case is a problem. 

fpc-devel maillist  -  fpc-devel at lists.freepascal.org
@Via ifmail 2:292/862 at fidonet, Tue Sep 5 2000 at 20:47 (2.14-tx8.10)

@Via D'Bridge 1.58 2:292/854  09/06 09:54

More information about the fpc-devel mailing list