Re: Source Scanner...

Trond Norbye wrote:
> Tor Norbye said:
>>If we add in specialized behavior like "ignore matches outside
>>java comments" it complicates the user model I think.
> 
> One could do one of the following:
> 
> a) Let the user select a source-scanner engine to use on a given file type
> the same way that the user may select the indention engine to use.
> 
> b) Let the user select something like:
> Ignore matches outside comments in known filetypes
> and list the filetypes.
> 
> c) Let the user specify the start/end tokens for a block comment, start
> token for an "end-of-line" comment for given file types (and let the user
> specify the extensions as regexs (java/c/c++ user similar comment style).

I still believe this complicates the user model, but perhaps
it's worth the extra complication. I like alternative (b) or (c)
the best, where obviously if we use (c) we should provide defaults
which are reasonable.  I assume the "known" filetypes would be java
and C/C++ files ( //, /* */), XML ( <!-- -->), JSP (<%-- --%>),
... anything else? I don't want the tasklist module to depend
on editor kits to do this scanning, it should all reside within
the tasklist module.

Well - would you like to implement this?   I think it's a higher
priority for you than for me :)

-- Tor