gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gnunet-scheme] 114/324: config: parser: More TODOs about the configurat


From: gnunet
Subject: [gnunet-scheme] 114/324: config: parser: More TODOs about the configuration format.
Date: Tue, 21 Sep 2021 13:22:34 +0200

This is an automated email from the git hooks/post-receive script.

maxime-devos pushed a commit to branch master
in repository gnunet-scheme.

commit 8f041a1762721dd25dcf1959d04816b8f8d3974a
Author: Maxime Devos <maximedevos@telenet.be>
AuthorDate: Thu May 13 16:53:37 2021 +0200

    config: parser: More TODOs about the configuration format.
    
    * gnu/gnunet/config/parser.scm
      (cs:unbraced-end/nested, cs:unbraced-end): Point out some
      inconsistencies with bash.
---
 gnu/gnunet/config/parser.scm | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gnu/gnunet/config/parser.scm b/gnu/gnunet/config/parser.scm
index a691d21..022449e 100644
--- a/gnu/gnunet/config/parser.scm
+++ b/gnu/gnunet/config/parser.scm
@@ -356,7 +356,9 @@ indicates the type of variable expansion found, as in
     (define cs:$-or-close (char-set #\$ #\}))
     ;; TODO: should #\0 be included?  It seems to be
     ;; ‘merely’ an artifact of the C implementation.
+    ;; TODO: add #\{?
     (define cs:unbraced-end/nested (char-set #\/ #\\ #\0 #\ #\}))
+    ;; TODO add #\{, #\} here, I guess? For consistency with bash.
     (define cs:unbraced-end (char-set #\/ #\\ #\0 #\ ))
 
     (define (parse-expandable* text start end nested?)

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]