Walter,

Is there an email address I can use to submit some functions for your review into std.path?  I used the email that is on your N.G. postings, but I don't know if my work email stomped on my outgoing or any potential incoming.

-Kramer

Kramer wrote:
> Walter,
> 
> Is there an email address I can use to submit some functions for your review
> into std.path?  I used the email that is on your N.G. postings, but I don't know
> if my work email stomped on my outgoing or any potential incoming.
> 
> -Kramer
> 
> 

Just from curiosity, because I did the same thing today, what functions are you submitting to std.path?

In article <dt4vmb$62s$1@digitaldaemon.com>, bobef says...
>
>Kramer wrote:
>> Walter,
>> 
>> Is there an email address I can use to submit some functions for your review into std.path?  I used the email that is on your N.G. postings, but I don't know if my work email stomped on my outgoing or any potential incoming.
>> 
>> -Kramer
>> 
>> 
>
>Just from curiosity, because I did the same thing today, what functions are you submitting to std.path?

Nice.  Looks like there's at least 2 people who want some more path functionality. <g>

Here's what I have:
getRoots
isRoot
containsRoot
normPath  // normalize a path; similar to the Python version
// http://docs.python.org/lib/module-os.path.html
isNormPath
normCase  // normalize the case
normSep  // normalize the separators for the given os
join  // variadic join
absPath  // includes a private isAbs because the one in std.path doesn't seem to
// be working
expandPath  // similar to the Ruby version
// http://www.rubycentral.com/ref/ref_c_file.html#expand_path

Of course, the private isAbs would eventually be removed (and I really hope I don't need a stronger pair of glasses, because from what I've seen it isn't working -- at least on Windows; that'd be nice if I was wrong).

What functions are you submitting?

-Kramer

P.S. - Sorry if any of the spacing is screwed up; I go through the web interface and it doesn't always play nice with the formatting.

Kramer wrote:
> In article <dt4vmb$62s$1@digitaldaemon.com>, bobef says...
>> Kramer wrote:
>>> Walter,
>>>
>>> Is there an email address I can use to submit some functions for your review
>>> into std.path?  I used the email that is on your N.G. postings, but I don't know
>>> if my work email stomped on my outgoing or any potential incoming.
>>>
>>> -Kramer
>>>
>>>
>> Just from curiosity, because I did the same thing today, what functions are you submitting to std.path?
> 
> Nice.  Looks like there's at least 2 people who want some more path
> functionality. <g>
> 
> Here's what I have:
> getRoots
> isRoot
> containsRoot
> normPath  // normalize a path; similar to the Python version
> // http://docs.python.org/lib/module-os.path.html
> isNormPath
> normCase  // normalize the case
> normSep  // normalize the separators for the given os
> join  // variadic join
> absPath  // includes a private isAbs because the one in std.path doesn't seem to
> // be working
> expandPath  // similar to the Ruby version
> // http://www.rubycentral.com/ref/ref_c_file.html#expand_path
> 
> Of course, the private isAbs would eventually be removed (and I really hope I
> don't need a stronger pair of glasses, because from what I've seen it isn't
> working -- at least on Windows; that'd be nice if I was wrong).
> 
> What functions are you submitting?
> 
> -Kramer
> 
> P.S. - Sorry if any of the spacing is screwed up; I go through the web interface
> and it doesn't always play nice with the formatting.
> 
> 

I was thinking to make variadic join. It is nice not make double efforts...

I want to submit:

getRelativePath
getFullPath (expands relative path)
getDrive (works with \\networkname under windows)
cleanPath (removes ..\ .\ from path)
fixPath (replaces backslashes (relative to std.path.sep) with slasehes (i.e. makes / to \ under windows and vice versa under linux)

"bobef" <bobef@lessequal.com> wrote in message news:dt4vmb$62s$1@digitaldaemon.com...
> Just from curiosity, because I did the same thing today, what functions are you submitting to std.path?

I received both of your emails about it. I guess we'll have to do a merge of the best of both!

Also, for submissions to std.path, I'll need an explicit release into the public domain, as I'm making std.path public domain.

Walter Bright wrote:

> Also, for submissions to std.path, I'll need an explicit release into the public domain, as I'm making std.path public domain. 

What is an "explicit release"?

In article <dt5400$a5l$1@digitaldaemon.com>, Walter Bright says...
>
>
>"bobef" <bobef@lessequal.com> wrote in message news:dt4vmb$62s$1@digitaldaemon.com...
>> Just from curiosity, because I did the same thing today, what functions are you submitting to std.path?
>
>I received both of your emails about it. I guess we'll have to do a merge of the best of both!
>
>Also, for submissions to std.path, I'll need an explicit release into the public domain, as I'm making std.path public domain.
>
>

Great!  I'll be sending my source tonight (no access to it at work).

"bobef" <bobef@lessequal.com> wrote in message news:dt55k7$bd3$1@digitaldaemon.com...
> Walter Bright wrote:
>
>> Also, for submissions to std.path, I'll need an explicit release into the public domain, as I'm making std.path public domain.
>
> What is an "explicit release"?

Explicitly saying you are placing it into the public domain. Imagine you're a lawyer looking at this - the less ambiguous, the better.

Walter Bright wrote:
> "bobef" <bobef@lessequal.com> wrote in message news:dt55k7$bd3$1@digitaldaemon.com...
>> Walter Bright wrote:
>>
>>> Also, for submissions to std.path, I'll need an explicit release into the public domain, as I'm making std.path public domain.
>> What is an "explicit release"?
> 
> Explicitly saying you are placing it into the public domain. Imagine you're a lawyer looking at this - the less ambiguous, the better.
> 
> 

I hate this shit. Here I place this source and allow everyone to do whatever he can imagine with it, but I will not be responsible for anything. In other words 'bobef license 1.0': use without restrictions at your own risk.

(by the way one line is change from the source I sent today)

On Sat, 18 Feb 2006 04:32:04 +1100, Kramer <Kramer_member@pathlink.com> wrote:

> In article <dt4vmb$62s$1@digitaldaemon.com>, bobef says...
>>
>> Kramer wrote:
>>> Walter,
>>>
>>> Is there an email address I can use to submit some functions for your review
>>> into std.path?  I used the email that is on your N.G. postings, but I don't know
>>> if my work email stomped on my outgoing or any potential incoming.
>>>
>>> -Kramer
>>>
>>>
>>
>> Just from curiosity, because I did the same thing today, what functions
>> are you submitting to std.path?
>
> Nice.  Looks like there's at least 2 people who want some more path
> functionality. <g>

Add another person. My Build utility has a number of extentions to std.path too. Maybe I should subit them as well.

char[] GetCurDir(char pDrive)
char[] GetInitCurDir()
Bool IsRelativePath(char[] pPath)
char[] CanonicalPath(char[] pPath, bool pFinal = true)
char[] ReplaceExtention(char[] pFileName, char[] pNewExtention)
bool MakePath(char[] pNewPath)
char[] AbbreviateFileName(char[] pName, char[][] pPrefixList = null)
char[] LocateFile(char[] pFileName, char[] pPathList)


-- 
Derek Parnell
Melbourne, Australia