Share

Gobo Eiffel Project

Tracker: Bugs

5 KL_WINDOWS_FILE_SYSTEM has trouble with weird unix name - ID: 2853675
Last Update: Comment added ( ericb )

For instance take this path

a+path := "/tmp/bug/a\\\\!@#$%^&*()-_=+|`~[]{} ;:,.<>%"'z'/src"

inherit
KL_SHARED_FILE_SYSTEM

code:
file_system.pathname_from_file_system (directory (a_path),
windows_file_system)


it won't handle the \\\\ as what it is, it resolves it as a simple
directory separator "/"



Jocelyn FIAT ( jfiat ) - 2009-09-07 16:16

5

Closed

Wont Fix

Eric Bezault

kernel

trunk

Public


Comment ( 1 )

Date: 2009-09-07 17:34
Sender: ericbProject Admin

If you want to handle unix-like pathnames, you should use
KL_UNIX_FILE_SYSTEM.

Now if you want to handle pathnames where both / and \ are recognized as
directory separators, then I'm not sure that the pathname that you provide
as example is valid. For example replace all \ by /. Is the resulting
pathname a valid unix pathname? The routines in KI_FILE_SYSTEM mention in
their header comments that they only make sense if the pathname is valid in
the underlying file system. If not, then the result is undefined. The
result that you get actually looks pretty good to me knowing that input is
not valid.


Attached File

No Files Currently Attached

Changes ( 5 )

Field Old Value Date By
status_id Open 2009-09-07 17:34 ericb
resolution_id None 2009-09-07 17:34 ericb
assigned_to nobody 2009-09-07 17:34 ericb
allow_comments 1 2009-09-07 17:34 ericb
close_date - 2009-09-07 17:34 ericb