Re: Undoing ExtractRelativePath
From: Marc Rohloff (dont_at_mailme.com)
Date: 12/03/03
- Next message: Yorai Aminov (TeamB): "Re: access violation"
- Previous message: Michael Winter: "Re: Access violation AFTER program exit !!"
- In reply to: Steve Moss: "Re: Undoing ExtractRelativePath"
- Next in thread: Steve Moss: "Re: Undoing ExtractRelativePath"
- Reply: Steve Moss: "Re: Undoing ExtractRelativePath"
- Reply: Rob Kennedy: "Re: Undoing ExtractRelativePath"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 3 Dec 2003 17:00:56 -0500
Steve Moss wrote on 3 Dec 2003 09:18:18 -0700 ...
<3fce1ada$1@newsgroups.borland.com>
> No. Read my message in full, where I said "I presume that if you have a
> relative path then you know what path it
> is relative to (well, if you don't, it's not much use ;-))" Then ...
Assuming is not always a good idea. For example Delphi will store
relative or absolute paths in the .dpr depending. When you read them
back you have to decide what they want.
Also a user can type in any path he likes. You would probably want to
make sure you can handle them sensibly. The way I described is the way
they would work at say a DOS prompt. (OK, So I'm old fashioned)
Also there is a PathCombine API call. I don't know if this handles all
the situations.
Marc Rohloff
marc rohloff at bigfoot dot com
- Next message: Yorai Aminov (TeamB): "Re: access violation"
- Previous message: Michael Winter: "Re: Access violation AFTER program exit !!"
- In reply to: Steve Moss: "Re: Undoing ExtractRelativePath"
- Next in thread: Steve Moss: "Re: Undoing ExtractRelativePath"
- Reply: Steve Moss: "Re: Undoing ExtractRelativePath"
- Reply: Rob Kennedy: "Re: Undoing ExtractRelativePath"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|