On Wed, 20 Sep 2017 20:38:23 +0200 (CEST)
Michael Van Canneyt via Lazarus wrote:
>[...]
> Currently not, I think.
> All the more reason to move everything to FCL in a unified codebase.
+1
> Or use your suggestion and use something like
>
> Type
> {$IFDEF
On Wed, 20 Sep 2017, Marcos Douglas B. Santos via Lazarus wrote:
On Wed, Sep 20, 2017 at 3:02 PM, Michael Van Canneyt via Lazarus
wrote:
On Wed, 20 Sep 2017, Marcos Douglas B. Santos via Lazarus wrote:
On Wed, Sep 20, 2017 at 12:36 PM, Michael Van Canneyt
On Wed, Sep 20, 2017 at 3:02 PM, Michael Van Canneyt via Lazarus
wrote:
>
>
> On Wed, 20 Sep 2017, Marcos Douglas B. Santos via Lazarus wrote:
>
>> On Wed, Sep 20, 2017 at 12:36 PM, Michael Van Canneyt via Lazarus
>> wrote:
>>>
>>>
On Wed, 20 Sep 2017, Marcos Douglas B. Santos via Lazarus wrote:
On Wed, Sep 20, 2017 at 12:36 PM, Michael Van Canneyt via Lazarus
wrote:
These units work using UTF8. The DOM units use UnicodeString (UTF16).
Given that these units are quite stable in terms
On Wed, Sep 20, 2017 at 12:36 PM, Michael Van Canneyt via Lazarus
wrote:
>
> These units work using UTF8. The DOM units use UnicodeString (UTF16).
>
> Given that these units are quite stable in terms of functionality and
> maturity, it may be a good idea to move
On Wed, 20 Sep 2017, Marcos Douglas B. Santos via Lazarus wrote:
Hi,
Nowadays we have Unicode and so on.
Is there any reason to these units (Laz2_DOM, laz2_XMLRead, and
laz2_XMLWrite) still exists?
I've always used them, but days ago I needed to use XPath and the
xpath unit works using
Hi,
Nowadays we have Unicode and so on.
Is there any reason to these units (Laz2_DOM, laz2_XMLRead, and
laz2_XMLWrite) still exists?
I've always used them, but days ago I needed to use XPath and the
xpath unit works using objects from DOM unit, not laz2_DOM, and
because that my doubt.
Best