16.01.2013 17:31, Max Kellermann пишет: > Which would add useless overhead to non-Windows. MPD's internal path > names are always const char* (currently), and stuffing that into a > std::string will always allocate memory. There's no optimization for > that.
Well, I think this would not be significantly different from current situation. If I'm understanding right mapper layer anyway allocates memory for transitions between internal UTF-8 and file system encoding. Even if file system encoding is UTF-8. I'm just proposing change of mapper interface from char* <-> char* to char* <-> FileName which gives benefit in additional type system check for possible messing between two representations. So "overhead" is really for additional code correctness which I think is a good goal to sacrifice some cycles. -- Denis ------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
