> Patrik Stridvall <psÉleissner.se> writes:
>
> > It is a little confusion yes, but perhaps that is the price
> we must pay.
>
> For what? for having _fullpath declared in stdlib.h?
Aproximately yes.
> is it really
> that important?
It is not imporant but it would be nice, but you are probably right
there are enough problems as it is.
> > As a sidenote I have often wondered whether perhaps it would
> > be better to implement functions that exists are both ANSI and
> > UNICODE as just one implementation in a file that is compiled
> > twice. This could be extended to 32-bit UNICODE by compiling
> > them thrice...
>
> No thanks. The code is large enough already.
With the exception of debug info the code will not really be
that much larger. Debug info with GNU C is a chapter of its
own though, so perhaps you are right. It would solve the
16/32-bit UNICODE problem nicely though.
Of course it could be used for just the 16/32 bit UNICODE function,
but that would probably still increase code size to much. Sigh.
> > In short, I can see a lot of work to get everything to interact
> > properly, but I really can't see any fundamental teoretical
> problems.
>
> No, of course there is no theoretical problem. Just a few man-years of
> work.
I think you are being overly pessimistic, however that doesn't mean that
you can't be right. I know there is a _lot_ of work and it is not at all
obvious which is the best way to do it.
