Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2006-12

fpcdoc gives a lot of warnings

3 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Vincent Snijders

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

Reply by email

Graeme Geldenhuys
to Vincent Snijders

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.

Vincent Snijders wrote 27 lines
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 - http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Graeme Geldenhuys There's no place like S34° 03.168' E018° 49.342'

Reply by email

Michael Van Canneyt
to Vincent Snijders: If I use thhe fpc 2.1.1 version of fpdoc on the rtl documentation files, I get a lot of…
Vincent Snijders wrote 27 lines
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?

Hm. I don't know. , I think it is a whitespace issue: I assume it thinks there is too much whitespace between <descr> and the starting <p> tag. I'll have to check this.

Michael.

Reply by email