Ticket #5592 (closed Bugs: fixed)

Opened 4 years ago

Last modified 4 years ago

Use CP_ACP not CP_THREAD_ACP [windows]

Reported by: Sam Morris <sam@…> Owned by: bemandawes
Milestone: To Be Determined Component: filesystem
Version: Boost 1.46.1 Severity: Problem
Keywords: Cc:


I've seen a few posts to boost-dev stating that it is wrong to use CP_THREAD_ACP when converting between 'ANSI' and wide filesystem paths. CP_ACP should be used as well.

The issue was raised by Yechezkel Mett in but received no response.

Two other users also chimed in in the discussion started at


Change History

comment:1 Changed 4 years ago by bemandawes

  • Status changed from new to closed
  • Resolution set to fixed

Applied changeset 76500, reverting to CP_ACP.

I'm ambivalent about this fix in that we don't have a test case that demonstrates it is correct. My definition of "correct" is that filesystem operational functions resolve paths exactly the same way that standard library file stream constructors/open resolve paths.

If someone could submit a test case, it would be much appreciated.



Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.