# XMLType Class Source Code?

**URL:** <https://clarionhub.com/t/xmltype-class-source-code/6568>\
**Category:** questions\
**Tags:** class, xml\
**Created:** [September 5, 2023, 2:28am UTC](https://clarionhub.com/t/xmltype-class-source-code/6568 "2023-09-05T02:28:38Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon51095673](https://clarionhub.com/letter_avatar_proxy/v4/letter/a/f9ae1b/32.png) [@anon51095673](https://clarionhub.com/u/anon51095673)\
**Post date:** [September 5, 2023, 2:28am UTC](https://clarionhub.com/t/xmltype-class-source-code/6568/1 "2023-09-05T02:28:38Z")

</div>

Problem solved many thanks...

---

<div class="post-metadata">

**Author:** ![jslarve](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/e480ec/32.png) [@jslarve](https://clarionhub.com/u/jslarve)\
**Post date:** [September 5, 2023, 4:25am UTC](https://clarionhub.com/t/xmltype-class-source-code/6568/2 "2023-09-05T04:25:17Z")

</div>

looks like it’s compiled

 ![image](https://clarionhub-uploads.s3.eu-north-1.amazonaws.com/original/2X/7/7fc9cdea89dd19c5c56e296c9577c99e412e434e.png)

---

<div class="post-metadata">

**Author:** ![Bjarne\_Havnen](https://clarionhub.com/user_avatar/clarionhub.com/bjarne_havnen/32/1350_2.png) [@Bjarne\_Havnen](https://clarionhub.com/u/Bjarne_Havnen)\
**Post date:** [September 8, 2023, 3:18pm UTC](https://clarionhub.com/t/xmltype-class-source-code/6568/4 "2023-09-08T15:18:14Z")

</div>

Is this perhaps the wrapper classes that use the CenterPoint XML (clacpxml.dll)? To my knowledge, this was discontinued about the same time SV wrote their implementation, which is about 20 years ago.

---

<div class="post-metadata">

**Author:** ![jslarve](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/e480ec/32.png) [@jslarve](https://clarionhub.com/u/jslarve)\
**Post date:** [September 8, 2023, 3:57pm UTC](https://clarionhub.com/t/xmltype-class-source-code/6568/5 "2023-09-08T15:57:53Z")

</div>

If I had to guess based on a quick search, I’d say that DLL was in use by the IDE.

```auto
C:\Clarion10\bin>grep -i Clacpxml *.*
Binary file Claasl.dll matches
Binary file Clacpxml.dll matches
Binary file Cladct.dll matches

```

---

<div class="post-metadata">

**Author:** ![Bruce](https://clarionhub.com/letter_avatar_proxy/v4/letter/b/ccd318/32.png) [@Bruce](https://clarionhub.com/u/Bruce)\
**Post date:** [September 10, 2023, 11:16am UTC](https://clarionhub.com/t/xmltype-class-source-code/6568/7 "2023-09-10T11:16:29Z")

</div>

If you need to deal with XML, the real “simple” option is just to use xFiles.  
[https://www.capesoft.com/accessories/xFilessp.htm](https://www.capesoft.com/accessories/xFilessp.htm)

That _is_ shipped as source code, includes both a streaming and tree parser, and simply deals with complex, or simple, xml. There’s even [capesoft.com/xfilescode](http://capesoft.com/xfilescode) to generate the matching clarion structures and code for you.

For JSON there’s an equivalent jFiles.  
[CapeSoft jFiles 3](https://www.capesoft.com/accessories/jFilessp.htm) and  
[capesoft.com/jfilescode](http://capesoft.com/jfilescode)

Both are on special until the end of September.

But this is just the easy way to do XML and JSON. If you prefer to write your own code, then by all means go for it. It’s not hard since both formats are just text files. All it’ll take is a few days of your time.

---

<div class="post-metadata">

**Author:** ![jslarve](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/e480ec/32.png) [@jslarve](https://clarionhub.com/u/jslarve)\
**Post date:** [September 10, 2023, 2:33pm UTC](https://clarionhub.com/t/xmltype-class-source-code/6568/8 "2023-09-10T14:33:54Z")

</div>

What happened to getting rid of XML and moving to JSON? I’m having trouble keeping up.

---

<div class="post-metadata">

**Author:** ![Bruce](https://clarionhub.com/letter_avatar_proxy/v4/letter/b/ccd318/32.png) [@Bruce](https://clarionhub.com/u/Bruce)\
**Post date:** [September 10, 2023, 3:34pm UTC](https://clarionhub.com/t/xmltype-class-source-code/6568/9 "2023-09-10T15:34:16Z")

</div>

I prefer JSON, but there’s an aweful lot of legacy xml out there. XML is massivly more complicated, and bigger enterprisd systems can make use of some of that complication.

So JSON isnt really a replacement for XML , but more a replacement for “most of XML” where XML was overkill. (Which is the case for most Clarion usage)

---

<div class="post-metadata">

**Author:** ![vitesse](https://clarionhub.com/user_avatar/clarionhub.com/vitesse/32/837_2.png) [@vitesse](https://clarionhub.com/u/vitesse)\
**Post date:** [September 10, 2023, 11:52pm UTC](https://clarionhub.com/t/xmltype-class-source-code/6568/12 "2023-09-10T23:52:53Z")

</div>

> [@anon51095673](#):
>
> “All it’ll take is a few days of your time.”

yes if you value your time then xFiles for XML and jFiles for JSON are well worth getting.

> [@anon51095673](#):
>
> We have an early version of String T from Net Talk 6 but we will get the lastest version.

both xFiles4 and jFiles3 require StringTheory3 so getting the latest ST is a good start - and ST is also useful for so many other things. I often say that once you start using ST and adjust your thinking, you will never look back and will likely wonder how (or indeed why) you ever got by previously without it.

bias disclaimer: while I don’t work for Capesoft, I’ve had a hand in much of the code in ST. (But having said that, I am certainly not the only person who loves ST.)

---

<div class="post-metadata">

**Author:** ![anon51095673](https://clarionhub.com/letter_avatar_proxy/v4/letter/a/f9ae1b/32.png) [@anon51095673](https://clarionhub.com/u/anon51095673)\
**Post date:** [September 11, 2023, 12:05am UTC](https://clarionhub.com/t/xmltype-class-source-code/6568/13 "2023-09-11T00:05:15Z")

</div>

It took 5 minutes to hook up the classes… we arnt new to classes or CPP…

Problem solved … and since its solved with a generic OOP solution it solved in every app that has managed queues…

Many thanks..
