Saxon » SaxonC

Reviewing the documentation changes, I'd like to understand this better.

1. Does the length limit for cwd only apply on PHP?
2. Have we imposed this limit for the cwd when creating a SaxonProcessor, or is it an inherited limit from the PHP getcwd() function (which is used as the default)?
3. What about using the 2-arg constructor SaxonProcessor(boolean $license, string $cwd)? If you supply $cwd here does the length limit apply or not?
4. In the documentation update, it says that the limit does not apply when using the SaxonProcessor.setcwd() method. What about setcwd() on Xslt30Processor and XsltExecutable?

Debbie Lockett wrote in #note-2:

Reviewing the documentation changes, I'd like to understand this better.

1. Does the length limit for cwd only apply on PHP?

Yes

2. Have we imposed this limit for the cwd when creating a SaxonProcessor, or is it an inherited limit from the PHP getcwd() function (which is used as the default)?

We have rightly or wrongly imposed this limit.

3. What about using the 2-arg constructor SaxonProcessor(boolean $license, string $cwd)? If you supply $cwd here does the length limit apply or not?

This limit does not apply in this case

4. In the documentation update, it says that the limit does not apply when using the SaxonProcessor.setcwd() method. What about setcwd() on Xslt30Processor and XsltExecutable?

Yes it does not apply on the other Processors.

I've committed an edit for the documentation update, to hopefully be a bit clearer.