On Sun, Jul 30, 2017 at 5:06 AM, Michael Van Canneyt
wrote:
>
>
> On Sat, 29 Jul 2017, Marcos Douglas B. Santos wrote:
>
>> FPC/Lazarus always tried stay compatible with Delphi... thus, why the
>> FPC XML classes is so different than Delphi classes?
>
>
> Because the FPC classes predate the Delphi
On Sun, Jul 30, 2017 at 4:30 AM, Sven Barth via fpc-pascal
wrote:
>> I have a FPC/Lazarus project that will be compatible with Delphi. I
>> would like to know whether I need to create wrappers to encapsulate
>> the differences between them or there is a simple way to do that.
>>
>> A 3rd lib could
On Sat, 29 Jul 2017, Marcos Douglas B. Santos wrote:
Hi,
FPC/Lazarus always tried stay compatible with Delphi... thus, why the
FPC XML classes is so different than Delphi classes?
Because the FPC classes predate the Delphi classes.
They were based directly on the W3 DOM specifications.
Am 30.07.2017 09:30 schrieb "Sven Barth" :
>
> Am 30.07.2017 02:01 schrieb "Marcos Douglas B. Santos" :
> >
> > Hi,
> >
> > FPC/Lazarus always tried stay compatible with Delphi... thus, why the
> > FPC XML classes is so different than Delphi classes?
Addendum: FPC's XML library probably also comes
Am 30.07.2017 02:01 schrieb "Marcos Douglas B. Santos" :
>
> Hi,
>
> FPC/Lazarus always tried stay compatible with Delphi... thus, why the
> FPC XML classes is so different than Delphi classes?
>
> Delphi XML is interface-based. There exists IXMLDocument, IXMLNode and so
on.
> FPC has just classes.
Hi,
FPC/Lazarus always tried stay compatible with Delphi... thus, why the
FPC XML classes is so different than Delphi classes?
Delphi XML is interface-based. There exists IXMLDocument, IXMLNode and so on.
FPC has just classes.
I have a FPC/Lazarus project that will be compatible with Delphi. I
w
