On Sep 16, 9:48 am, markm <[EMAIL PROTECTED]> wrote:
> On Sep 16, 7:51 am, Rich Hickey <[EMAIL PROTECTED]> wrote:
>
> ...
>
> > The workaround I came up with fails to filter the bridge method in
> > org.jscience.physics.amount.Amount. I'm still looking into this issue.
>
> >http://groups.google.com/group/jvm-languages/browse_frm/thread/a64c75...
>
> > Rich
>
> Below is the source code from Amount.divide and Amount.times for the
> long and double parameter versions. Other than the obvious
> substitution of variable and operator names, the times <double> and
> divide <double> methods are structurally equivalent. The times <long>
> and divide <long> method have one difference: the divide method makes
> use of local variables <min> and <max> -- as do both double methods --
> the times <long> method directly assigns the result of calculation
> into the m._minimum and m._maximum fields.
>
> Could this difference be triggering the jdk/vm 1.6 into treating the
> <whatever the name for the aggregate of> the 'times' methods
> differently from the <whatever the name for the aggregate of> the
> 'divide' method?
>
No. The problem relates to times being inherited from
GroupMultiplicative<G>.
I understand what is happening, just trying to find a workaround that
will work for this case and not break on others (e.g. StringBuilder)
Rich
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this group, send email to clojure@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---
