PathFinder status

[xoft]

The interface looks good enough, maybe a few small tweaks such as returning a const reference to (an internal) cPath object, rather than a naked ptr to it; those can be done as we go.

I'm just afraid that if you write your code the way you wrote the interface, you're in for a hell lot of restyling to match MCS's code style and make it past the CheckBasicStyle.lua script. We use a_CamelCase for params, CamelCase for function names, m_CamelCase for member variables; there needs to be a space after each comma ("param1, param2"), on both sides of math operators ("a = b + c") and pointer and reference declarations ("cClass & a_Param"). We use tabs for indenting, and continuation lines should have one single level of indent more than the parent line (not vertical alignment). Closing braces should be on the same indent level as the opening braces, both standing on separate lines; if a closing parenthesis is on a separate line, it should be on the same level as the line it's closing. Comments need to have at least two spaces in front of them and one space after the double-slash, and should start with a capital letter.