Savannah CVS Surfing
- Log of /3dldf/3dldf/Group/CWEB/3DLDFtex.pdf.gz
Parent Directory
Revision
1.38 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Jan 13 17:08:03 2009 UTC (10 months, 1 week ago) by
lfinsto1
Branch:
MAIN
Changes since
1.37: +3952 -471 lines
Diff to
previous 1.37
Added sample of drawing a trochoid pattern.
Images are skipped in this sample to avoid the PostScript and
PDF files being overly large.
Revision
1.28 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Feb 24 10:44:44 2008 UTC (20 months, 4 weeks ago) by
lfinsto1
Branch:
MAIN
Changes since
1.27: +1 -1 lines
Diff to
previous 1.27
In `matrices.web' and `complex.web':
Now conditionally compiling code in all functions that make
use of types or functions from the GSL library.
Revision
1.21 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Dec 23 18:55:30 2007 UTC (23 months ago) by
lfinsto1
Branch:
MAIN
Changes since
1.20: +1 -1 lines
Diff to
previous 1.20
It seems that it won't be possible for me to get matrix multiplication
to work at present. The version of the GNU Scientific Library that
I have available (1.6) is quite out-of-date and I will need to find
another system to work on.
Revision
1.12 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Nov 29 21:54:24 2007 UTC (23 months, 3 weeks ago) by
lfinsto1
Branch:
MAIN
Changes since
1.11: +1 -1 lines
Diff to
previous 1.11
Working on |class Matrix|, its functions, and the parser rules for
the corresponding 3DLDF type `matrix'.
Unlike the transformation matrices contained in `transforms',
the number of rows and columns of `matrices' can be set by the user.
|class Matrix| uses data types and functions defined in the GNU Scientific Library
(GSL). The code from that library is conditionally compiled, depending
on whether it's available on the system on which GNU 3DLDF is installed.
If the GSL is unavailable, the `matrix' type is non-functional
and the functions of `class Matrix' will return "unsuccessfully",
but no parser errors should occur.
Revision
1.11 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Nov 29 21:36:31 2007 UTC (23 months, 3 weeks ago) by
lfinsto1
Branch:
MAIN
Changes since
1.10: +1 -1 lines
Diff to
previous 1.10
Working on |class Matrix|, its functions, and the parser rules for
the corresponding 3DLDF type `matrix'.
Unlike the transformation matrices contained in `transforms',
the number of rows and columns of `matrices' can be set by the user.
|class Matrix| uses data types and functions defined in the GNU Scientific Library
(GSL). The code from that library is conditionally compiled, depending
on whether it's available on the system on which GNU 3DLDF is installed.
If the GSL is unavailable, the `matrix' type is non-functional
and the functions of `class Matrix' will return "unsuccessfully",
but no parser errors should occur.
Revision
1.9 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Nov 28 17:21:14 2007 UTC (23 months, 3 weeks ago) by
lfinsto1
Branch:
MAIN
Changes since
1.8: +4 -5 lines
Diff to
previous 1.8
Started working on |class Matrix| and the 3DLDF types |matrix| and
|matrix_vector|. They use the data types and functions for matrices
defined in the GNU Scientific Library (GSL), if the latter is present.
If it isn't, they will be non-functional.
They are currently non-functional, anyway, but I'm working on them.
Revision
1.8 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Nov 28 15:27:58 2007 UTC (23 months, 3 weeks ago) by
lfinsto1
Branch:
MAIN
Changes since
1.7: +1 -1 lines
Diff to
previous 1.7
Started working on |class Matrix|. It will use the GSL (GNU Scientific Library)
`gsl_matrix', if the GSL is available. Otherwise, it will be non-functional.
Revision
1.7 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Nov 28 14:04:07 2007 UTC (23 months, 3 weeks ago) by
lfinsto1
Branch:
MAIN
Changes since
1.6: +1 -1 lines
Diff to
previous 1.6
Added |struct Predicate|, member functions, and parser declarations and
rules. The parser declarations and rules are currently commented-out.
There are many possible tests that can be performed on objects of various types.
It may therefore be desirable to reduce the number of rules needed for the
predicates. |predicate_variables| can be used for this purpose. However,
they have a significant disadvantage, since the names that refer to them
cannot be followed directly by other variable names in the input file. The
reason is that the beginning of the second variable name is interpreted as a `tag'
continuing the name of the |predicate_variable|, since blank space is ignored in this
context. The second variable name must therefore be separated somehow from the
name of the |predicate_variable|. Enclosing it in parentheses works without
having to account for this in the parser rules. Another possibility would be to
use a comma or some other symbol to separate the two items. However, this
would need to be accounted for in the parser rules.
I will not be using this approach for the present.
Revision
1.5 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Nov 25 16:27:25 2007 UTC (23 months, 4 weeks ago) by
lfinsto1
Branch:
MAIN
Changes since
1.4: +4 -210 lines
Diff to
previous 1.4
BUG FIX: It is now possible to use `xpart <point or transform expression>',
`ypart <point or transform expression>', in expressions. Previously,
this didn't work, because the same `vector' of `real' numbers was used
for the "parts" as for the suffixes of variables.
Revision
1.2 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Oct 26 10:41:44 2007 UTC (2 years ago) by
lfinsto1
Branch:
MAIN
Changes since
1.1: +1 -1 lines
Diff to
previous 1.1
Made changes to various files that became necessary when I accidentally
deleted my local `CWEB' directory. A number of problems arose when
I tried to recover it, which I have now corrected.
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
select a symbolic revision name using the selection box, or choose
'Use Text Field' and enter a numeric revision.