I'm using fcl-xml to parse a XML data from a TMemoryStream/TStringStream and
noted it can parse streams with a maximum capacity of 4096 bytes, why can't it
receive bigger streams?.
The maximum capacity is defined in the constructor of TXMLStreamInputSource, in
XMLRead.pp.
Leonardo M. Ramé wrote:
I'm using fcl-xml to parse a XML data from a TMemoryStream/TStringStream and
noted it can parse streams with a maximum capacity of 4096 bytes, why can't it
receive bigger streams?.
The maximum capacity is defined in the constructor of TXMLStreamInputSource, in
Thanks Sergey.
I tought that was why my program was stopping with an assertion in procedure
TNodePool.AddExtent of dom.pp, the assertion dissapears when I work with
smaller XML files.
BTW: the file worked with older versions of fcl-xml, now I'm using the trunk
version because it no longer
On 12 Jan 2010, at 19:12, Thomas Nelson wrote:
I seem to have come across a minor problem and don’t know how to fix it.
Utilizing the \examples\odbc\testodbc.pp module with FPC 2.2.4 everything
compiles fine
When I upgraded to FPC 2.4.0 I get an error message (please see attached
On Thu, 14 Jan 2010, Jonas Maebe wrote:
On 12 Jan 2010, at 19:12, Thomas Nelson wrote:
I seem to have come across a minor problem and don’t know how to fix it.
Utilizing the \examples\odbc\testodbc.pp module with FPC 2.2.4 everything
compiles fine
When I upgraded to FPC 2.4.0 I get an
Leonardo M. Ramé wrote:
Thanks Sergey.
I tought that was why my program was stopping with an assertion in procedure
TNodePool.AddExtent of dom.pp, the assertion dissapears when I work with
smaller XML files.
BTW: the file worked with older versions of fcl-xml, now I'm using the trunk
Yes!, thank you very much Sergei.
Leonardo M. Ramé
http://leonardorame.blogspot.com
--- On Thu, 1/14/10, Sergei Gorelkin sergei_gorel...@mail.ru wrote:
From: Sergei Gorelkin sergei_gorel...@mail.ru
Subject: Re: [fpc-devel] XML Stream capacity
To: FPC developers' list
Hello people,
I've discovered that (at least on win32) the compiler (2.2.2 and 2.4.0)
refuse to overwrite an invalid PPU file. It just stops.
One typical case is when PPU creation had previously failed due to disk
problems (e.g. out of room) or compilation abort, whatever, resulting in
Nikolai Zhubr schrieb:
Hello people,
I've discovered that (at least on win32) the compiler (2.2.2 and 2.4.0)
refuse to overwrite an invalid PPU file. It just stops.
One typical case is when PPU creation had previously failed due to disk
problems (e.g. out of room) or compilation abort,
Thank you all very much –
Making the changes you suggested fixed my problems.
Back to work now :)
Thomas Nelson
Director Information Technology, Information Systems
CoxHealth
thomas.nel...@coxhealth.com
Phone: (417) 269-8961
Mobile: (417) 459-3528
Fax: (417) 269-2133
CoxHealth – a Top 100
I don't think that people will be happy if the compiler just deletes
their ppus if it can't read it for any reason. The compiler cannot know
if it can recreate the ppu when it deletes it.
Can't it just be made to treat a damaged/unreadable ppu in the same way
as an outdated or incompatible
Nikolai Zhubr schrieb:
15.01.2010 0:01, Florian Klaempfl:
I don't think that people will be happy if the compiler just deletes
their ppus if it can't read it for any reason. The compiler cannot know
if it can recreate the ppu when it deletes it.
Well, when a user asks compiler to compile,
12 matches
Mail list logo
