Best way might be to discard the concept that the indent under the
parameter occurs. Maybe just do 1 or 2 characters. Choosing 2 works
fine - for some reason 1 causes wrapping to break which is odd.
Also need to add code so it wraps the parameters themselves. Looking
at it I'm realizing that that
Luc Maisonobe wrote:
Hello,
Since release of 1.2, several people have asked for advices on using the
estimation and optimization packages imported from mantissa. This showed
these packages were poorly designed (you can blame me for that). After
one of the discussions on this topic, issue MATH-17
Lets try to keep changes.xml up to date and also include JIRA: FOO-xyz
references in commit messages so tickets get the svn info added and the
maven changes report (and release notes generated from changes.xml)
remain accurate. By convention, we stack changes in changes.xml with
most recent ad
Luc Maisonobe wrote:
Phil Steitz a écrit :
l...@apache.org wrote: }
/**
+ * Returns true iff both arguments are equal or within the range
of allowed
+ * error (inclusive).
+ * + * @param x first value
+ * @param y second value
+ * @param eps the amount of
Phil Steitz a écrit :
> l...@apache.org wrote: }
>>
>> /**
>> + * Returns true iff both arguments are equal or within the range
>> of allowed
>> + * error (inclusive).
>> + * + * @param x first value
>> + * @param y second value
>> + * @param eps the amount of absolut
l...@apache.org wrote: }
/**
+ * Returns true iff both arguments are equal or within the range of allowed
+ * error (inclusive).
+ *
+ * @param x first value
+ * @param y second value
+ * @param eps the amount of absolute error to allow
+ * @return true if the
