[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: [ANN] LuaAnnotate - C code comments externally stored but displayed inline / documenting Lua code
- From: steve donovan <steve.j.donovan@...>
- Date: Sun, 28 Nov 2010 14:07:44 +0200
On Sat, Nov 27, 2010 at 8:37 PM, David Manura <dm.lua@math2.org> wrote:
> http://googlecode.blogspot.com/2008/07/looks-good-to-me-source-code-review.html
Yes, to directly see it in action:
http://code.google.com/p/support/source/browse/trunk/scripts/googlecode_upload.py?spec=svn70&r=70
> It's a technicality, and other storage formats could be supported.
> The single file seemed easier to manage, at least for the small Lua
> sources.
The annot-file-per-source-file seemed the first thought, but on second
thought it works better in one file
> BTW, one related idea I was thinking about was some type of text
> editor plugin that would allow you to edit multiple files in the same
> buffer
It's literate programming meets Web 2.0 if it happened in the browser ;)
The relationship between text in the buffer and actual file
representation does not of course have to be one-to-one. E.g. one
could hack SciTE so that the save-to-file went through a Lua filter.
Annotations provide a nice visual indication of this.
steve d.