[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
From: |
Patrice Dumas |
Date: |
Sat, 25 May 2024 04:03:30 -0400 (EDT) |
branch: master
commit 3dd3b9280e95a5f969a2a25dedac5dd6cf646fb2
Author: Patrice Dumas <pertusus@free.fr>
AuthorDate: Fri May 24 21:38:33 2024 +0200
Update tp/TODO
---
tp/TODO | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/tp/TODO b/tp/TODO
index 095d981c75..e1a02c2da1 100644
--- a/tp/TODO
+++ b/tp/TODO
@@ -57,11 +57,6 @@ Document *XS_EXTERNAL_FORMATTING *XS_EXTERNAL_CONVERSION?
Delayed bugs/features
=====================
-Add the possibility to add text to a parsed document by restarting
-parsing, when called as parse_texi_piece or parse_texi_line, by
-storing the parser document state not already in document in document.
-
-
Gavin idea to use see/See for cross references in --plaintext output.
More generally, the plaintext ref_commands formatting code
could be completly different from the Info code, which is the current
@@ -251,6 +246,16 @@ Future features
===============
+Add the possibility to add text to a parsed document by restarting
+parsing, when called as parse_texi_piece or parse_texi_line, by
+storing the parser document state not already in document in document.
+There would be a customization variable to set the parser to be
+restartable, and then parse_texi_piece and parse_texi_line could pass
+a document to retrieve the parsing state. This should probably
+wait for a clear use case. Currently, the parser is never reused
+for different documents in the main codes, only in specific tests.
+
+
For converters in C, agreed with Gavin that it is better not to
translate a perl tree in input, but access directly the C tree that
was setup by the XS parser.