>> If I now say that error codes are 32bit wide, the upper 16bit could
>> hold the line number, the next 8 bits a file ID and the lowermost
>> bits the real error code. This would be a quite effective means to
>> find out the source code origin of returned error codes even in
>> non-debug builds.
>
> It would, but I'd consider module errors an API mistake to begin
> with.
Well...
> For the past ten years everyone has been comparing FT error codes
> using good old equality operator. If no one uses a feature, there's
> no point developing it further.
Actually, I don't know whether this feature gets used.
> If anything, it should be removed.
Hmm. I rather favour to improve it, together with advertising FT_ERR
and friends. So I won't do anything right now.
Werner
_______________________________________________
Freetype mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype
