Whilst some errors might be common, such as 'unknown-encoding', others can be quite specific - for example the Binary 'index-out-of-range' specifically says that you are trying to access (with a possibly non-zero footprint) some data outside the size of piece of binary data, not any other circumstance. Whilst this may have some similarity with other 'out-of-range' errors it's really designed to be trapped specifically within Binary. I'd really prefer to keep the modules as self-contained as practicable. Whilst Binary will often be used with File or other EXPath modules, there is no necessity to do so and keeping the modules tight and clean makes them easier to both package, document and test. On 12/12/2013 15:04, Michael Kay wrote: > I think it's going to be much easier for users if we let each module > have its own namespace and put all the functions and error codes for > that module in that namespace. > > Michael Kay > Saxonica > > On 12 Dec 2013, at 15:02, Innovimax W3C <innovimax+w3c@gmail.com > <mailto:innovimax+w3c@gmail.com>> wrote: > >> This is a general question on EXPath Module >> >> Are the Module supposed to be standalone or can we share a bit of >> information (like error codes and namespace) ? >> >> If we share something, can we start gathering data for a EXPath >> Common Module ? >> >> Mohamed >> > -- *John Lumley* MA PhD CEng FIEE john@saxonica.com <mailto:john@saxonica.com> on behalf of Saxonica Ltd
Received on Thursday, 12 December 2013 15:33:27 UTC