On Fri, 8 Apr 2011,michael.vancanneyt worte:
The whole idea of interfaces is to avoid multiple inheritance.
Hm. I don't believe that.
One of the major points of interfaces is indeed to avoid the problems
of multiple class inheritance (diamond problems - i.e. problems caused by
conflicting impl
On Tue Apr 12, michael.vancanneyt worte:
On Tue, 12 Apr 2011, Andreas Dorn wrote:
On Fri, 8 Apr 2011, michael.vancanneyt worte:
The whole idea of interfaces is to avoid multiple inheritance.
Hm. I don't believe that.
One of the major points of interfaces is indeed to avoid the proble
Hi there,
In the discussion about resourcestrings I read that the RTL now uses
codepage-aware strings for FileIO.
So I wonder what kind of codepages do you use for FileIO?
The Windows-documentation calls Filenames "opaque sequence of WCHARs".
https://msdn.microsoft.com/en-us/library/windows/des
On Fri, 25 Sep 2015, Michael Van Canneyt wrote:
> It uses UTF16 on windows, not a codepage aware string.
> So if you use widestring for all your filename strings, there will be no
> problem. No conversions will happen.
If I understand that correctly, it stores the filename in a string that
has
All in all Graeme is right. FPC looks pretty much broken to me, too.
For my projects I pulled the emergency-break on anything FPC.
The most serious flaws for me of FPC 3.0 are:
- assuming that it's possible to assign an encoding to every string
- using an (unsafe) guess about the encoding fo
