Problems with native_file_string() on windows

[nobody]

It seems I have stumbled upon a known bug with
path::native_file_string() on windows.

The returned std::string object can not be destroyed
when going out of scope.

A similar error occurs when using
directory_iterator::leaf().

Has anyone developed a patch for this yet?

Thanks,
barry
bazbishop@btinternet.com


see also:
http://aspn.activestate.com/ASPN/Mail/Message/boost/1968006
http://archives.free.net.ph/message/20051111.035907.1ed81e73.en.html

[beman_dawes]

Logged In: YES 
user_id=51042

Hum... What do you mean by "can not be destroyed when going
out of scope"?

The return from these functions is by value, so destruction
is automatic.

Could you post a sample of your code?

--Beman

[beman_dawes]

Logged In: YES 
user_id=51042

In view of the lack of sample code, I'm closing this. Since
the object involved is automatic (stack) allocation, I can't
see any possible "cannot be destroyed when going out of
scope" issue.

Perhaps the OP meant something else, but I don't have any
plausible guess for what that might be.
  
--Beman