[e-lang] Wiki makes updoc excess authority bug urget
Mark S. Miller
markm at cs.jhu.edu
Tue Dec 5 12:08:36 CST 2006
https://sourceforge.net/tracker/index.php?func=detail&aid=1211101&group_id=75274&atid=551529
Now that we have updoc scripts on our new wiki, which is publicly
editable, this bug has become urgent. I have accordingly promoted it to
the highest priority.
It's unclear what the right answer to this is. In the meantime, I have wget'ed
the current state of the wiki, which presumably has not yet been edited to
contain malicious updoc code. I have started editing the online wiki pages to
pass updoc in accord with the results of updoc'ing my local (and increasingly
stale, but presumably safe) snapshot.
As the bug report states, some adaptation of the powerbox pattern may be the
right answer. But it's unclear how to balance various usability issues as
applied to updoc. Alternatively, we could provide a simulated environment to
the updoc scripts that had no external authority. This is a lot of work, but
would also lead to more reproducible results.
The updoc in the released version of E failed to updoc many of these pages,
because some peculiarities of the conversion revealed some flaws in updoc.
Specifically, updoc would recognize
<pre># E sample
as beginning a bit of code to be evaluated, but would not if there was
whitespace between the <pre> tag and the "#". The updoc in the SVN head now
does recognize this.
Similarly, the srcccheck.e script was using a crude method to extract the
extension of a file that failed for file paths containing "."s. The srccheck.e
in the SVN fixes that too.
--
Text by me above is hereby placed in the public domain
Cheers,
--MarkM
More information about the e-lang
mailing list