Re: Ideas for path separator character
- Posted by akusaya at gmx.net
Apr 12, 2006
From what I know, in linux you can have any character for the file
name (including ? and * and \) except / because it is used for dir
separator and nul (byte 0)
So if your string is not nul terminated, you can use that :)
> posted by: Al Getz <Xaxo at aol.com>
> Hello there,
> Im looking for ideas for a single character to use as a path separator.
> The character shouldnt be anything that could be contained within a
> path (win or lin).
> Problem is, every char you pick 'could' be contained in the
> path at the end where the program arguments can be. For example:
> Using * as a separator char:
> *c:\mydir\myfile.exe* *c:\otherdir\otherfile.exe*
> These paths seem to be clearly defined as bewteen * chars.
> Problem comes up if one day someone finds they need to use the * char
> as argument to their program such as:
> c:\mydir\file2.exe *
> Now trying to put that within * chars looks like this:
> *c:\mydir\file2.exe **
> which is not clear to the program reading this line because it will
> think the program path ends after the second * char.
> Yes, maybe it can see that there is one more * but there are other
> situations too, such as maybe the program needs two in a row as
> argument to tell it to do something:
> *c:\mydir\file2.exe **
> Now it's impossible to tell what the 'user' intends.
> Ok, having said that, maybe two in a row to indicate a literal * char,
> but any other ideas out there?
> Environments use semicolon to sep paths, but im wondering if there are
> any programs out there that use a semi as a possible argument, or
> are they always avoided because of this?
> Al
> My bumper sticker: "I brake for LED's"
> From "Black Knight":
> "I can live with losing the good fight,
> but i can not live without fighting it".
> "Well on second thought, maybe not."
|
Not Categorized, Please Help
|
|
