[fpc-pascal] fpcdoc gives a lot of warnings

Graeme Geldenhuys graemeg.lists at gmail.com
Wed Dec 13 12:42:24 CET 2006


I'm experiencing the same thing in fpGUI, but thought it was because
we did a lot of refactoring so the .xml and .pas units are out of
sync.  I never investigated it further.

Graeme.


On 12/13/06, Vincent Snijders <vsnijders at quicknet.nl> wrote:
> Hi,
>
> If I use thhe fpc 2.1.1 version of fpdoc on the rtl documentation files, I get a lot
> of warnings like:
>
> Writing 7520 pages...
> [<no context>] Invalid description (illegal XML element: "#text")
> [<no context>] Invalid description (illegal XML element: "#text")
> [<no context>] Invalid description (illegal XML element: "#text")
> [<no context>] Invalid description (illegal XML element: "#text")
> [<no context>] Invalid description (illegal XML element: "#text")
> [<no context>] Invalid description (illegal XML element: "#text")
> [#rtl.strutils.AnsiMatchText] Invalid description (illegal XML element: "#text")
> [#rtl.strutils.AnsiMatchText] Invalid description (illegal XML element: "#text")
> [#rtl.strutils.AnsiMatchText] Invalid description (illegal XML element: "#text")
> [#rtl.strutils.AnsiMatchStr] Invalid description (illegal XML element: "#text")
> [#rtl.strutils.AnsiMatchStr] Invalid description (illegal XML element: "#text")
> [#rtl.strutils.AnsiMatchStr] Invalid description (illegal XML element: "#text")
>
> Do you have an idea, what causes this? Is the new parser adding #text nodes, that
> the old parser didn't? Is fpdoc's checking too strict?
>
> Vincent
> _______________________________________________
> fpc-pascal maillist  -  fpc-pascal at lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-pascal
>


-- 
Graeme Geldenhuys

There's no place like S34° 03.168'  E018° 49.342'



More information about the fpc-pascal mailing list