From joe at novelcap.com  Thu Oct 23 19:59:35 2008
From: joe at novelcap.com (Joseph Haykov)
Date: Thu, 23 Oct 2008 13:59:35 -0400
Subject: [Rd] normalizePath bug (PR#13199)
In-Reply-To: <4900B936.9030407@stats.uwo.ca>
References: <20081023144504.33D9F282BEBF@mail.pubhealth.ku.dk>
	<4900B936.9030407@stats.uwo.ca>
Message-ID: <op.ujhn9le5ict22x@laptop>

Actually, it's a new file that I plan on writing to, so while the  
directory C:\\DOCUME~1\\JOSEPH~1\\LOCALS~1\\Temp\\RtmpolZ4Vy exists, the  
file file72ae2cd6.txt does not. However, this was working fine in version  
2.6.2. If you're saying that the reason why this doesn't work is because  
the file does not exist, I can easily work around the issue.

Best regards,


Joe Haykov


On Thu, 23 Oct 2008 13:49:42 -0400, Duncan Murdoch <murdoch at stats.uwo.ca>  
wrote:

> On 10/23/2008 10:45 AM, joe at novelcap.com wrote:
>> Full_Name: Joseph Haykov
>> Version: 2.8.0
>> OS: Windows
>> Submission from: (NULL) (216.189.177.202)
>>    
>> normalizePath("C:\\DOCUME~1\\JOSEPH~1\\LOCALS~1\\Temp\\RtmpolZ4Vy\\file72ae2cd6.txt")
>>  returns: "\0354xl|\a&#144;\001 $v\001?y8"
>>  instead of returning:
>>  "C:\\Documents and Settings\\Joseph Haykov\\Local
>> Settings\\Temp\\RtmpolZ4Vy\\file72ae2cd6.txt"
>>  By the way, this works correctly in version 2.6.2
>
> I see the problem, and will look into it.  It first started failing in  
> 2.7.0; it's not a new bug.
>
> But I'm not sure it's a bug, since that directory doesn't exist on my  
> system, and the function is documented to give undefined results in that  
> case.  Does that file exist on your system?
>
> Duncan Murdoch



[Rd] normalizePath bug (PR#13199)
Joseph Haykov