lucy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucy Wiki] Update of "MeetUp" by MarvinHumphrey
Date Sat, 04 Apr 2015 00:20:46 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucy Wiki" for change notification.

The "MeetUp" page has been changed by MarvinHumphrey:
https://wiki.apache.org/lucy/MeetUp?action=diff&rev1=3&rev2=4

Comment:
Thwart !WikiLinks.

  
  Clownfish/Lucy-specific discussion questions for interfaces:
  
-  1.  Should Lucy's Query class be an interface instead of an abstract class?  How about
Analyzer, Searcher, Matcher, Collector, Compiler, IndexReader, DataReader, DataWriter, Lexicon,
Posting, Folder, FileHandle, Lock, and SortExternal -- all of which are abstract classes?
+  1.  Should Lucy's Query class be an interface instead of an abstract class?  How about
Analyzer, Searcher, Matcher, Collector, Compiler, !IndexReader, !DataReader, !DataWriter,
Lexicon, Posting, Folder, !FileHandle, Lock, and !SortExternal -- all of which are abstract
classes?
-  1.  There are a handful of Lucy classes which are designed to be subclassed by users but
are not abstract: QueryParser, IndexManager, Schema, FieldType, and Highlighter.  Why is it
challenging to change these to interfaces?
+  1.  There are a handful of Lucy classes which are designed to be subclassed by users but
are not abstract: !QueryParser, !IndexManager, Schema, !FieldType, and Highlighter.  Why is
it challenging to change these to interfaces?
   1.  How can we change the Clownfish callback mechanism to be based on interfaces instead
of classes?
   1.  Should Obj#Hash_Sum be moved to a "Hasher" interface?  Should Obj#Clone be moved to
a "Cloner" interface?  Should Obj have any methods at all?
  

Mime
View raw message