Dominique Devienne wrote:
But this doesn't work if a batch of files is not self contained, i.e.
depends on classes in the next batch. Using batching has the potential
to break a compilation that would otherwise work fine in one go.
Well, so far testing does not expose this issue.
It's always a little scary to hear of 20K+ files in a project. There
should be independent sub-projects, but that's a different story.
Wast majority of these files are automatically generated and
structure of the project is dictated by external conditions which are hard
or impossible to change.
I would advise:
1) To use an attribute name similar to <apply>'s, which does batching.
I've used 'batchSize' which is by default set to "-1" which means
"disable batching".
I think this is safe enough and is backward-compatible.
2) Also provided test and document patches, to increase your patch's
chances to be accepted. Emphasis should be put in the doco that this
is a "dangerous" attribute.
OK. I understand. This will take a little while, because my spare time
is very limited.
Regards,
Sergey.
*---------------------------------------------
[EMAIL PROTECTED] http://es.os2.ru/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
