RE: XML Calabash: New option, changed XProcConfiguration constructor

*looked at the code*

No, but the code will complain if it aint something it expects..

(supported values are: he, pe, and ee)

;-)

-----Oorspronkelijk bericht-----
Van: David Lee [mailto:dlee@calldei.com]
Verzonden: vrijdag 2 december 2011 15:29
Aan: 'Geert Josten'; 'Norman Walsh'; 'XProc Dev'
Onderwerp: RE: XML Calabash: New option, changed XProcConfiguration
constructor

is the possible values of "edition" defined somewhere ? Like say an Enum ?



----------------------------------------
David A. Lee
dlee@calldei.com
http://www.xmlsh.org


-----Original Message-----
From: Geert Josten [mailto:geert.josten@dayon.nl]
Sent: Friday, December 02, 2011 9:10 AM
To: Norman Walsh; XProc Dev
Subject: RE: XML Calabash: New option, changed XProcConfiguration
constructor


How about allowing both constructors and having the first call the second
with a 'defaulted' "saxon-HE" as default value (or whatever the syntax of
that edition string should be)?

Grtz

-----Oorspronkelijk bericht-----
Van: Norman Walsh [mailto:ndw@nwalsh.com]
Verzonden: vrijdag 2 december 2011 15:04
Aan: XProc Dev
Onderwerp: XML Calabash: New option, changed XProcConfiguration
constructor

Hi folks,

To address issue 22, https://github.com/ndw/xmlcalabash1/issues/22
I added a new option to XML Calabash. All well and good. But it was
convenient
(to me) to change the constructor for XProcConfiguration.

Is this inconvenient for integrators? If you've got XML Calabash
integrated
into some other project and will find the change from

  new XProcConfiguration(boolean schemaAware)

to

  new XProcConfiguration(String edition, boolean schemaAware)

please let me know. I'll move things around a bit if it makes your
lives easier.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 413 624 6676
www.marklogic.com

Received on Friday, 2 December 2011 15:55:23 UTC