[sword-devel] Av11n and coverage

Troy A. Griffitts scribe at crosswire.org
Fri Feb 10 13:39:04 MST 2012

Hey guys.  I'm remember this thread from a while back am to lazy to go 
back and look.

Please remind me why we want a .conf entry and not a call like:

SWMgr library;
SWModule *kjv = kjv = library.getModule("KJV");
VerseKey testKey = "jn.3.16";

// --------------------------------
ListKey range = kjv.getModuleScope();
// --------------------------------

range = testKey;

if (range.Error()) cerr << testKey << " is not within the range: " << 
range.getRangeText() << endl;

The only thing missing is the SWModule::getModuleScope() method which 
could easily be written to scan the module and produce an appropriate 

The .conf file is an opportunity for inconsistency.  It can be a useful 
checksum or a pain in the butt maintenance nightmare and I'm thinking 
the latter.

On 02/10/2012 04:35 PM, David Haslam wrote:
> Let's not forget that some modules are for a work in progress by the
> translators.
> e.g. A New Testament only module may have plenty of cross-references to OT
> passages, in anticipation that the translation would one day eventually be
> completed.
> And - yes - as DM noted, xrefs for modules that are scope-restricted should
> be linkable for parallel modules that contain the missing books, etc.
> David
> --
> View this message in context: http://sword-dev.350566.n4.nabble.com/Av11n-and-coverage-tp4265350p4376618.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

More information about the sword-devel mailing list