From d9d11d517d07103690fd081b60c10fdb234ff12a Mon Sep 17 00:00:00 2001 From: Ludovic Courtès Date: Sat, 15 Mar 2008 15:16:24 +0100 Subject: Add `TODO' ideas. --- TODO | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) (limited to 'TODO') diff --git a/TODO b/TODO index 1855538..10512bb 100644 --- a/TODO +++ b/TODO @@ -1,6 +1,6 @@ -*- Org -*- -Copyright 2007 Ludovic Courtès +Copyright 2007, 2008 Ludovic Courtès Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright @@ -83,6 +83,16 @@ To that end, VList-based hash lists could come into play. Andy Wingo's **** Customs could be passed at engine instantiation time **** Main problem is `markup-writer' +*** Find a purely functional representation of ASTs + +[[http://pobox.com/~oleg/ftp/Scheme/parent-pointers.txt][Oleg's work on SXML parent pointers]] is probably a good source of +inspiration, especially the "parent pointers as thunks" approach: it's +simple and Just Works! + +In addition, we could have the resolution function add a VList "hash +list" (read: functional hash table) to the `document' node so that we +can do `document-lookup-node'. + ** Don't name markups using symbols Markups should be named using unforgeable objects, rather than symbols. This would be a step in the direction of "capability-object semantics". -- cgit v1.2.3