... Giggle.^2.1

If this is not the case for the license agreement I have chosen for Giggle (the Lesser Gnu Public License), then alert me, & I'll choose another license agreement & create a new release of Giggle. It is my intention that the license agreement for Giggle cover Giggle only.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... -i.^8.1

Why the two formats? The .tar.gz format is more common, but I prefer the .cpio.bz2 format, so I've decided to distribute both. Why do I prefer the second format? Because bzip2 compresses better than gzip & because using cpio is more fun than using tar. (Really. It's more fun to use cpio, mostly because of how flexible it is with find. More fun. That's the main reason, I swear.)

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... fail.^8.2

My test programs print nothing if they succeed so that you can glance at the list of tests as make runs them & easily determine whether they succeeded. After all, that's what you care about. You don't want or need to read through a long, ugly, stream of output from a bunch of test programs to determine whether the tests succeeded. Success or failure should be binary, & the common, desired case (success) should be easy to determine at a glance.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... form^8.3

That's this document, the one you're reading.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... /usr/local/include/CyberTiggyr/giggle/^9.1

It is installed there, by default.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... Giggle.^9.2

I recommend the -lgiggle form, just to be simple.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... notice.^9.3

I like the #include$<$CyberTiggyr/giggle/giggle.hxx$>$ form is preferable because the explicit path reminds what giggle.hxx is.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... program.^9.4

Future releases of Giggle might allow for multiple garbage collectors or for replacing garbage collectors. For now, you must specify the garbage collector exactly once, & you must do it before you do any allocation with Giggle.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... problem.^9.5

This actually depends on the Garbage Collector you have chosen for Giggle, but you should assume that it will cause problems.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... periods.^13.1

I haven't bothered to figure out if it's on the hour or only at midnight.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... consideration^14.1

The fewer objects a garbage collector has to consider, the faster it'll run, in general.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... deleted.^14.2

We're talking in theoretical, language-independant, C++-independant terms at the moment. Pretend that destructors don't exist, & bear with me.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... cost.^14.3

I mean, if we weren't concerned with run-time costs, we wouldn't be programming in C++.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.