> I've avoided the term post-it as I fear trademarks ;) I agree. :-)
> Let me know what you think. I'm happy to knock up a proof of concept > once we're happy with the spec. I agree. I think that it is one of correct ways to provide command interface. With it, both users and tool developers need not know the details of data structure including file format. I want the -l command (or with some options) to print like follows. +------------------------------ |#<line number> |<note> |... |#<line number> |<note> |... '##' at the first column is expanded to a single '#'. [Example] $ tagger -l main.c #10 This is main() of this program. ##include <stdio.h> is required. #22 The following operation should be fixed. #502 This code was derived from http://xxxxx/xxxxx/. $ _ With the output, it is easy for any tools to print the following source code according to their style. [main.c] +----------------------- | 1 /* | 2 * Program foo. | 3 */ | 4 #include <stdio.h> ... | 9 int |[tagger's notes]-------------------------- | This is main() of this program. | #include <stdio.h> is required. |------------------------------------------ | 10 main(int argc, char **argv) | 11 { ... |[tagger's notes]-------------------------- | The following operation should be fixed. |------------------------------------------ | 22 if (a = b = c) { ... |[tagger's notes]-------------------------- | This code was derived from http://xxxxx/xxxxx/. |------------------------------------------ |502 while (....) { ... By the way, does tagger require GLOBAL installed? -- Shigio YAMAGUCHI <[EMAIL PROTECTED]> - Tama Communications Corporation PGP fingerprint: D1CB 0B89 B346 4AB6 5663 C4B6 3CA5 BBB3 57BE DDA3 _______________________________________________ Bug-global mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-global
