On Jul 14, 2008, at 18:15, Andreas Delmelle wrote:
Just quickly ran Jeremias' test-app myself, and on Apple JVM (1.5),
the difference is +/-300ms for a million iterations, but not very
consistent. Sometimes StringBuffer operates slightly faster, other
times it's CharBuffer that wins. I gu
Peter,
Which file is this?
basedir ${basedir} build.gensrc.dir ${build.gensrc.dir}
immediately in front of line 352 to verify. It could be a mixed forward
and backslashed path.
Phil
Peter B. West wrote:
>
> bonekrusher wrote:
>> I will test this out later today on my home PC. I get a diffe
On Jul 14, 2008, at 08:44, Jeremias Maerki wrote:
I noticed that Andreas used CharBuffer in his initial patch for
#45390.
I was curious about the performance implications, so I wrote a little
micro-benchmark. The results:
So this is a single-threaded test. It might perform differently in a
he
Jeremias Maerki wrote:
How about:
An fo:table is wider than the available room in
inline-progression-dimension. Adjusting end-indent based on
overconstrained geometry rules (XSL 1.1, ch. 5.3.4)
I'd like to have the hint about overconstrained geometry in there
because this condition is not str
bonekrusher wrote:
I will test this out later today on my home PC. I get a different set of
errors on different machines.
In the mean time I ran a new svn check out (as you suggested) on my work PC
and got the same original error message e.g.
BUILD FAILED
C:\foptrunk2\trunk\build.xml:353: java.
On 14.07.2008 11:20:09 Chris Bowditch wrote:
> Chris Bowditch wrote:
>
>
>
> > I understand that is what happens behind the scenes, but IMO it is
> > meaningless to the average user. I think it makes sense to change the
> > message to:
> >
> > "table too wide for available page width"
> >
>
I will test this out later today on my home PC. I get a different set of
errors on different machines.
In the mean time I ran a new svn check out (as you suggested) on my work PC
and got the same original error message e.g.
BUILD FAILED
C:\foptrunk2\trunk\build.xml:353: java.io.IOException:
java
Chris Bowditch wrote:
I understand that is what happens behind the scenes, but IMO it is
meaningless to the average user. I think it makes sense to change the
message to:
"table too wide for available page width"
or similar. Then the user knows what they have to adjust in their FO.
Rathe
