Complete rewrite of NormalizePath

The former algorithm was based on the pseuocode
from the RFC, which is hard to follow, more suitable
when the path is in a single string, not a sequence
of segments.

The new algorithm uses two flags:
* isAbsolute - recognize that if the path starts out
  as an absolute path, it needs to stay that way.
* atDirectoryLevel - recognize that if we encounter
  a "." or "..", then it will be reduced by simply
  discarding it or going back/up one stop, but then
  we will be in a "directory" context, meaning that
  should we end the path at this point, there needs
  to be an empty-string segment to mark that the
  end of the path is reaching into a directory, not
  just referring to the directory.

0 files changed, 0 insertions, 0 deletions