1 Feb
2012
1 Feb
'12
9:25 p.m.
El 01/02/2012 11:27, Thorsten Ottosen escribió:
Alternatively, you can accept a boost::filesystem::path object, if you can live with that dependency. Then you have pushed the problem to the caller.
filesystem::path seems very useful, but I don't like the dependency (Interprocess is a header only lib) and I find path interface suboptimal. There is an open bug for wide-string/unicode support for Interprocess, so I'll need to find time (too much time I'm afraid) to study the issue in detail. By the way, I don't find the restriction of using plain ASCII characters for named objects. I think mutex, shm semaphore names don't badly need encoding support. file_mapping, on the other hand needs at least wide strings, at least in windows. Ion