This is just an annoyance of mine (both to me and caused by me :-)) that is
useful to clear up before eCos 3.0 rather than after since otherwise it
breaks .ecc files then. This names the X_TLOSS CDL option in the standard
way, that's all.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
Index: ChangeLog
===================================================================
RCS file: /cvs/ecos/ecos/packages/language/c/libm/current/ChangeLog,v
retrieving revision 1.26
diff -u -5 -p -r1.26 ChangeLog
--- ChangeLog 4 Sep 2007 14:26:08 -0000 1.26
+++ ChangeLog 20 Nov 2008 17:09:28 -0000
@@ -1,5 +1,9 @@
+2008-11-20 Jonathan Larmour <[EMAIL PROTECTED]>
+
+ * cdl/libm.cdl: Rename X_TLOSS CDL option to match normal convention.
+
2007-09-04 Stephen Finney <[EMAIL PROTECTED]>
2007-09-04 Jonathan Larmour <[EMAIL PROTECTED]>
* src/misc/infconst.c: Declare infinity byte order as dependent on
double byte order, not integer.
Index: cdl/libm.cdl
===================================================================
RCS file: /cvs/ecos/ecos/packages/language/c/libm/current/cdl/libm.cdl,v
retrieving revision 1.6
diff -u -5 -p -r1.6 libm.cdl
--- cdl/libm.cdl 24 Feb 2003 14:28:55 -0000 1.6
+++ cdl/libm.cdl 20 Nov 2008 17:09:28 -0000
@@ -177,15 +177,16 @@ cdl_package CYGPKG_LIBM {
signgam variable in thread-safe mode."
}
}
# OTHER CONFIGURATION SETTINGS
- cdl_option X_TLOSS {
+ cdl_option CYGNUM_LIBM_X_TLOSS {
display "Bessel function limit of significance"
flavor data
default_value 1.41484755040568800000e+16; # pi*(2**52)
legal_values 1 to 1e308; # FIXME
+ define X_TLOSS
description "
For the Bessel functions (j0(), j1(), jn(),
y0(), y1(), yn()) this option defines the
maximum absolute value of the ordinate
before we assume total loss of significance.
