+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
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:
Sun Java 1.4.2_16:
StringBuffer def: 6594 ms
StringBuffer 1024: 6609 ms
CharBuffer: 5250 ms
Sun Java 1.5.0_14:
StringBuffer
Chris Bowditch wrote:
snip/
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.
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:
On 14.07.2008 11:20:09 Chris Bowditch wrote:
Chris Bowditch wrote:
snip/
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.
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:
Jeremias Maerki wrote:
snip/
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
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:
snip /
So this is a single-threaded test. It might perform differently
Peter,
Which file is this?
echobasedir ${basedir} build.gensrc.dir ${build.gensrc.dir}/echo
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
On Jul 14, 2008, at 18:15, Andreas Delmelle wrote:
snip /
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
10 matches
Mail list logo
