Pavel Sanda wrote:
> hi,
>
> anybody against the change of this method name
> to be compatible camel case with the class itself?
chmm, we already have Buffer::absFileName. isn't possible
that something goes wrong in the code like:
Buffer::foo(){
foo2(...FileName(absFileName()....),absFileName(),...)
}
dont remember exact rules but iirc c++ naming lookup was
doing pretty wild actions like pulling in the namespace
of function arguments... so now there could be danger that
in certain constructions FileName::absFileName would be
chosen instead of Buffer::absFileName?
pavel
