19 messages in org.w3.xproc-devRe: Fileutils| From | Sent On | Attachments |
|---|---|---|
| Norman Walsh | May 25, 2009 11:58 am | |
| David A. Lee | May 25, 2009 2:21 pm | |
| Norman Walsh | May 25, 2009 2:26 pm | |
| Norman Walsh | May 25, 2009 3:11 pm | |
| Dave Pawson | May 25, 2009 10:04 pm | |
| mozer | May 25, 2009 11:34 pm | |
| Toma...@emc.com | May 26, 2009 12:19 am | |
| Norman Walsh | May 26, 2009 5:06 am | |
| Norman Walsh | May 26, 2009 5:07 am | |
| Norman Walsh | May 26, 2009 5:09 am | |
| Dave Pawson | May 26, 2009 6:49 am | |
| Norman Walsh | May 29, 2009 4:27 am | |
| Toma...@emc.com | May 29, 2009 4:47 am | |
| James Fuller | Jun 1, 2009 5:07 am | |
| Leif Warner | Jun 1, 2009 9:28 am | |
| James Fuller | Jun 1, 2009 9:43 am | |
| Norman Walsh | Jun 1, 2009 9:43 am | |
| James Fuller | Jun 1, 2009 10:17 am | |
| Norman Walsh | Jun 1, 2009 11:22 am |
| Subject: | Re: Fileutils | |
|---|---|---|
| From: | James Fuller (jame...@gmail.com) | |
| Date: | Jun 1, 2009 10:17:27 am | |
| List: | org.w3.xproc-dev | |
On Mon, Jun 1, 2009 at 6:43 PM, Norman Walsh <nd...@nwalsh.com> wrote:
James Fuller <jame...@gmail.com> writes:
<p:declare-step type="cxf:info"> <p:declare-step type="cxf:touch"> <p:declare-step type="cxf:tempfile"> <p:declare-step type="cxf:delete"> <p:declare-step type="cxf:mkdir"> <p:declare-step type="cxf:copy"> <p:declare-step type="cxf:move">
cool, could we add a fail-on-error option which is set to true by default on all the steps, but could be overridden if different behavior is desired.
We could. But do you really want to ignore failure for any of these?
mainly I would like to reduce the try/catch verbosity ... and yes we could add this option to every step ... but I think its pragmatic with respect to working with transient file systems. Prime example would be for using with cfx:delete; perhaps I would like to delete a file and its not there and I don't care.
also any thoughts on ?
cfx:head cfx:tail
They're sort of tricky wrt XML.
the main bifurcation is with binary or text ... easy enough to implement a pipeline doing this for example using optional p:exec step but mainly the value is with cross platform compatibility with these commands.
Jim Fuller