Am 19.06.2013 00:12, schrieb Fred van Stappen:
>then you'll need to write a wrapper around it which could
>for example utilize the "-vq" option to display a message id in front of
>each message the compiler writes.
Hello everybody.
I have finish the first part of sak (speecher assistive kit) fo
On 06/18/2013 02:35 PM, Marcos Douglas wrote:
Today I call WriteXMLFile(Doc, AFileName) but I have XML with 5G, 10G.. 30G...
What the best way to save "line by line"?
Why not push it through a stream compressor ?
-Michael
___
fpc-pascal maillist -
On Wed, 19 Jun 2013, Michael Schnell wrote:
On 06/18/2013 02:35 PM, Marcos Douglas wrote:
Today I call WriteXMLFile(Doc, AFileName) but I have XML with 5G, 10G..
30G...
What the best way to save "line by line"?
Why not push it through a stream compressor ?
You completely miss the point.
On 2013-06-19 08:47, Michael Van Canneyt wrote:
> The problem is that the source XML is completely in memory, which is why it
> takes so much memory after while.
+1
And if "logging" is the use case, XML is by far the worst format anybody
could choose.
Regards,
- Graeme -
__
On 06/19/2013 12:14 PM, Graeme Geldenhuys wrote:
XML is by far the worst format anybody could choose
Yep. bus as it is "Standard" some need to
Thus IMHO the way to go is to have the basic XML component work on
linked lists with binary data in memory and only when loading/saving use
an A
On Wed, 19 Jun 2013, Michael Schnell wrote:
On 06/19/2013 12:14 PM, Graeme Geldenhuys wrote:
XML is by far the worst format anybody could choose
Yep. bus as it is "Standard" some need to
Thus IMHO the way to go is to have the basic XML component work on linked
lists with binary data
On Wed, Jun 19, 2013 at 7:14 AM, Graeme Geldenhuys
wrote:
> On 2013-06-19 08:47, Michael Van Canneyt wrote:
>> The problem is that the source XML is completely in memory, which is why it
>> takes so much memory after while.
>
> +1
>
> And if "logging" is the use case, XML is by far the worst form
On Wed, Jun 19, 2013 at 8:29 AM, Michael Schnell wrote:
> On 06/19/2013 12:14 PM, Graeme Geldenhuys wrote:
>>
>> XML is by far the worst format anybody could choose
>
>
> Yep. bus as it is "Standard" some need to
>
> Thus IMHO the way to go is to have the basic XML component work on linked
>
On 06/19/2013 02:44 AM, Michael Schnell wrote:
On 06/18/2013 02:35 PM, Marcos Douglas wrote:
Today I call WriteXMLFile(Doc, AFileName) but I have XML with 5G,
10G.. 30G...
What the best way to save "line by line"?
Why not push it through a stream compressor ?
-Michael
__
On 06/19/2013 01:31 PM, Michael Van Canneyt wrote:
What do you think TXMLDocument and XMLWriter do ? Exactly this.
In fact I did thinks this until you stated "the source XML is completely
in memory" which misled me to the assumption that the XML text would be
in memory (the binary list is n
Hello.
I use a external C library (call parent-lib). That library uses a other
external library (call child-lib).
To compile a DLL using a external DLL with Microsoft Visual Studio, you need
the lib file of the child-lib.
If you want to dynamically load those libraries, you need to use "loadli
On Wed, 19 Jun 2013 13:31:45 +0200 (CEST)
Michael Van Canneyt wrote:
>
>
> On Wed, 19 Jun 2013, Michael Schnell wrote:
>
> > On 06/19/2013 12:14 PM, Graeme Geldenhuys wrote:
> >> XML is by far the worst format anybody could choose
> >
> > Yep. bus as it is "Standard" some need to
> >
> >
On 6/19/2013 06:14, Graeme Geldenhuys wrote:
On 2013-06-19 08:47, Michael Van Canneyt wrote:
The problem is that the source XML is completely in memory, which is why it
takes so much memory after while.
+1
And if "logging" is the use case, XML is by far the worst format anybody
could choose.
On Wed, Jun 19, 2013 at 1:48 PM, waldo kitty wrote:
> On 6/19/2013 06:14, Graeme Geldenhuys wrote:
>>
>> On 2013-06-19 08:47, Michael Van Canneyt wrote:
>>>
>>> The problem is that the source XML is completely in memory, which is why
>>> it takes so much memory after while.
>>
>>
>> +1
>>
>> And i
14 matches
Mail list logo
