🚀 go-pugleaf

Way back in the "good old days" before GCC took over all the HD real
estate I seem to be able to find, I used HSC and a hacked version of
dLibs.

For a long time now, I've been tinkering with a small/fast variant on
Dan Conroy's original MicroEmacs that was hacked for dLibs, converting
it to ANSI C and GCC and such, and as a result find myself needing an
equivalent of the dLibs fullpath().

For those of you not in the know, fullpath() would take a non-absolute
filespec (".\wombat.txt", "\frob\foo\lump\minor.mad", whatever) and
return to you an absolute pathname--that wonderful long thing with
drive spec and all that's such hell to type.

Now I've been looking through the GCC libraries, and the closest thing
I've found is _dos2unix() and its variants.  My question is, does that
actually resolve relative or incomplete pathspecs to be "canonical",
or does it just flip the path separators.

The answer to this question, plus any pointers on its use would be
much appreciated.  I've got the source, it's just a little
more...involved than I care to get right at this particular moment.

Thanks,