Hess, Philip J ha scritto:
Michael,
Thanks for pointing that out about ReadXMLFile. I see that my code has
the same memory leak.
I think the confusion lies in that with Delphi once TXMLDocument has
been used to create the object, the file is loaded by setting the
object's FileName property, so it would appear logical to do the
equivalent with FPC: call ReadXMLFile and pass the TXMLDocument object.
But looking at the XmlRead.pp source I see that ReadXMLFile's
TXMLDocument parameter is "out".
Another point of confusion is that the corresponding WriteXMLFile
function takes an already-instantiated TXMLDocument, whereas ReadXMLFile
does not.
Question: Is there any place where someone could know this without
inspecting the XmlRead.pp source and understanding the implications of
that "out" param?
Thanks.
-Phil
Thanks for the tips.
Yes the cause of my bad code was Delphi-related.
So that "bug" is caused by something else... but how can a
"bad-compiled" fpc give problems only on a component (DOM) and not
everywhere...?
I'm a little confused, I'll try to install a pre-compiled older version
this afternoon.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
