Is there any chance of moving “packages/chm/src/fasthtmlparser.pas”
to a more publicly accessible location inside the FCL? eg: fcl-base?
That way other FCL packages could use that code as well (I think)? I’m
working on new code which will eventually live in the FCL. The code
needs a simple HTML-like tag parser. I started writing my own, then
while searching for something else in the FCL I stumbled across the
fasthtmlparser.pas unit which is exactly what I needed (no need for my
html parser any more). But I don't need anything else from the CHM
So for now I made a copy of that unit, but that definitely doesn’t seem
like the best way of doing things. Is there a better why of handling this?
On 2016-05-04 15:10, Graeme Geldenhuys wrote:
> So for now I made a copy of that unit, but that definitely doesn’t seem
> like the best way of doing things. Is there a better why of handling this?
Umm, in hind sight, simply adding the “fasthtmlparser” to the uses
clause in my code seems to work. I don’t need a copy of that unit after
all. FPC manages to find in somehow (not sure how yet - FPC magic <wink>).
Either way, I see the fpindexer also uses that unit. So maybe it is
worth moving it to a more public [obvious] location in FCL?