From dca8114e3be0f85a703790348f627fbc7d0c03d0 Mon Sep 17 00:00:00 2001 From: jthorn Date: Sun, 18 Aug 2002 16:36:07 +0000 Subject: expand description of naming conventions git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/LocalInterp/trunk@85 df1f8a13-aa1d-4dd4-9681-27ded5b42416 --- src/GeneralizedPolynomial-Uniform/Lagrange/README | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to 'src') diff --git a/src/GeneralizedPolynomial-Uniform/Lagrange/README b/src/GeneralizedPolynomial-Uniform/Lagrange/README index ec861ac..56f5d1a 100644 --- a/src/GeneralizedPolynomial-Uniform/Lagrange/README +++ b/src/GeneralizedPolynomial-Uniform/Lagrange/README @@ -18,11 +18,17 @@ fns.maple These files define the interpolation functions, coefficients, etc, for the Maple code in [123]d.maple -[123]d.cube.order?.smooth0.c +[123]d.cube.order?.smooth?.c These files are the individual cases for the interpolation. Each file defines a separate function. Each file just #defines a bunch of macros, then #includes "../template.c" to get the - actual interpolation code. The functions are named + actual interpolation code. Unfortunately, the ISO C standard + only guarantees 31 characters for function names (in fact, it + doesn't even guarantee that for external names -- they may be + limited by a system linker -- but I quietly ignore that and + assume I can use 31), so the functions are named in a somewhat + cryptic manner: + 123456789 123456789 123456789 1 LocalInterp_ULagrange_1dcube_10 LocalInterp_ULagrange_1dcube_20 LocalInterp_ULagrange_1dcube_30 -- cgit v1.2.3