Change namespace separator to ".."

[shapes.git] / VERSION

0.6.0.3
The first line of this file shall be the last tagged version string.  The version history may be filled in at any time, but when a version is tagged, the current date shall be added on the first line of the release notes for the version being tagged.

  Version history
===================

====( 0.6.0.3 )====
2014-01-30

Maintenance release.

Brings changes (some of which were bugfixes) for improved compatibility with modern tools: Automake, Autoconf, ImageMagick, libpng, and Clang.

With the new optional build dependency OpenSSL, the generated PDF files  will have file identity information, bringing them closer to PDF/A conformance.

Bugfixes include:
-  PDF generation (addressing a GhostScript warning).
-  A use after free detected by AddressSanitizer.


====( 0.6.0.2 )====
2010-10-02

Important maintenance release.

Bugfixes include:
-  The man page and HTML documentation are now installed when building from distribution even if Saxon is not present.
-  Fixes problems with 'make clean' aborting due to failing include directives.
-  Fixes compilation error when building without libpng.


====( 0.6.0.1 )====
2010-10-01

Maintenance release.

Bugfixes include:
-  Compatibility with modern TeX distributions that generate PDF 1.5 output.
-  Fixes compilation when the FreeType library version is at least 7.0.1 but less than 10.0.0.


====( 0.6.0 )====
2010-06-02

Bringing in FreeType and fontconfig.  So far, the only supported font format is TrueType, and the support of this format is in no way complete.  Still, this version marks the start of a more serious treatment of text and fonts in Shapes.  Currently supported features include access to glyph outlines and painting (as well as clipping with respect to) text using both embedded and outlines fonts.  Better font support and more features related to text formatting are expected in the future.

Backwards incompatible change: "TeX" is no longer the keyword of a special form.  It now behaves as an ordinary function, although the implementation still detects calls with a literal string argument during program analysis.  Expressions like (TeX ("$x^{2}$")) are deprecated and shall be replaced by [TeX ("$x^{2}$")].  The old special form will still be allowed for some (not very long) time, but a warning message will inform the user about the need to switch to a function call.

Other new features include:  Wider support for folds, and a new efficient implementation of ranges.  New syntax %last refers to last position in a container.  New syntax allows mutators to be called as part of an insertion sequence.  New atomic data type for characters.  New state type for one-dimensional arrays.  The new dynamic variable @spot is an alternative to [spot (0m,0m)].  Shapes now ship with shapes-mode, which comes with some new features and bugfixes, and is now described in the Shapes on-line documentation.

Bugfixes include:
-  Workaround for Flex not being compatible with modern C++ compilers.
-  A configuration bug caused errors when libpng was present, but not libjpeg.
-  Miter limit is a float, and values less than 1 are not allowed.
-  Default value for @text_knockout was wrong.


====( 0.5.2 )====
2009-12-14

Now supporting native include of some raster image formats, namely PNG and JPEG.  JPEG file inclusion is supported by means of the JPEG facilities defined in the PDF standard, while parts of the feature-rich PNG format are supported with help from the libpng library.  Compared to using \includegraphics in a TeX label, including images directly in Shapes is more reliable since there is no need to detect when a TeX label needs to be rebuilt.

Command line option --iteration=false prevents reuse of stored labels (in addition to preventing the label database file from being written).  This feature would have been of greater value before the release of this version, since problems with raster images not being updated was the main reason behind it.

The shapes-mode for Emacs is now using a new technique for indentation.

Bugfixes include:
-  Configuration of Saxon after they changed their naming scheme.


====( 0.5.1.2 )====
2009-11-02

This is a bugfix release.

Bugfix:
-  The man page silently failed to build, and an empty man page was installed.


====( 0.5.1.1 )====
2009-08-22

This is a bugfix release.

Bugfix:
-  Fixed C++ conformity issue causing build failure with modern C++ compiler.


====( 0.5.1 )====
2009-08-19

A minor version increment with important new features, one remarkable removal of a bad feature, changed syntax, and more.

The two big news are the path-to-path approximation and an improved analysis of user programs.

The path-to-path approximation is available through <approximator>.  It captures a very natural way to select a point on a path (but the implementation was a little bit involved, which is why the feature hasn't appeared until now).

The improved analysis keeps track of the free states in every expression, and is therefore able to detect that a code bracket which only mutates its own states is a pure expression.

With this version, the old and ugly procedures have been removed from the language.  They were never used, and made programs much more difficult to analyze.  Without procedures, there was no longer any need for the old "!" syntax, and hence the old "!!" was changed to "!".

Bugfixes include:
-  Errors in the CSS for HTML documentation.
-  Subpaths at end of closed path.
-  A 3D arrowhead was trying to fill a non-closed path.


====( 0.5.0 )====
2009-05-18

Stepping the version from 0.4.x to 0.5.x is motivated by the arriaval of the interactive mode of the compiler.  The interactive mode could make it easier to teach and learn Shapes, and the it is also used extensively by the new debugging facility.  The debugging facility, represented by the debugger state #db (available in the interacitve mode only), provides common debugging tools such as examination of the current evaluation state (lexical and dynamic environments, and backtrace), breakpoints, and stepping.  While the true usefulness of the interactive mode during normal use of Shapes remains unclear, it implementation brings important improvements to the compiler design.

The shapes-mode for Emacs has been updated, and includes some support for the interactive mode (try it with "M-x run-shapes" in Emacs!).

This release also contains the new arrowhead <ShapesArrow>.  It generally looks better than <MetaPostArrow>, and replaces <MetaPostArrow> in most examples and extensions.

Now supporting the PDF feature to clip with a text object as mask.

More documentation.

Bugfixes include:
-  Random number generation was completely broken when compiling with recent gcc g++ compiler.
-  Installation of HTML documentation was broken, causing the documentation index.html to be overwritten by the "project web" index.html.
-  The PDF text state was not updated correctly in some situations.


====( 0.4.3.1 )====
2009-03-10

This release combines compatibility fixes for GCC 4.3 with some install-related improvements.

Bugfixes include:
-  Sloppy C++ has been cleaned up to compile with GCC 4.3.


====( 0.4.3 )====
2008-12-22

This release comes with many long awaited, but backwards incompatible changes.  Merry Christmas!

New string construction syntax.  There are now three ways to enter strings, two of which have no escape characters, and a third that is only partly human-readable.  Most notably, the newline is now entered as the four character construct "{n} (having no special meaning inside the human-readable strings).

New operator for sending one argument through a function from the left.  For instance, the following two lines are equivalent:
  [stroke [immerse [circle 1cm]]]
  [circle 1cm] >> immerse >> stroke
Note that the operator is left associative.

Changed operator precedence and associativity rules.  Biggest change is that [] is now left associative to give good support for hard-wired curry functions.  This means that all old chains of [], changes into chains of >> (in reversed left-right order).  The new priority of | allows many old parentheses to be removed, but needs only a few new to be inserted.  Operator precedence and associativity can now be found in the syntax documentation.

There is now a prelude.  The standard prelude relieves the user from bringing in the most common extensions with ##needs.

Many functions in the standard prelude were renamed.

Bleed boxes are used instead of bounding boxes to determine size of final page.  Used by TeX (which takes a setting from @TeX_bleed) to remedy an old problems with bounding boxes coming out slightly too small from pdfLaTeX.

Improved Emacs support.

More documentation.

Buxfixes include:
-  Prevention of endless elementary path computation.
-  Problems with thunks in user dynamic variable declarations.
-  Character encoding setting in the Emacs shapes-mode.


====( 0.4.2.1 )====
2008-12-13

(Celebrating Gustaf's thirtieth birthday.)

This is primarily (but not only) a bugfix release.

Bugfixes:
-  For some build setups, not all xsl files were included in distributions.
-  Exponents in scientific notation.
-  Removed confusion regarding which dynamic environment to use in tack-on operations.


====( 0.4.2 )====
2008-12-02

GPL and copyright notes have been inserted in all non-trivial files.

A logo has been introduced.  Do not consider it final!

New notation, including more ASCII fall-backs.  The change of notation for functions is not backwards compatible!

Introduced mutators for states.  Old, global, non-pure functions were removed -- not backwards compatible!

New shapes-mode for Emacs.

Stuff for transforms, including fields (components as well as predicates), a <chop> method, and a kind of real Schur decomposition in 3D.

Lots of new documentation.

Source code for methods of types in Shapes has been reorganized.

Bugfixes include:
-  Including FlexLexer.h in distribution.
-  Annoying internal errors when displaying source locations were removed.


====( 0.4.1 )====
2008-10-16

(Celebrating my thirtieth birthday.)

Improved build process for the documentation.

Introducing exit codes.

Bugfixes include:
-  Building the correct index.html at the top of the HTML documentation.
-  Lost JPG files in the HTML documentation were found by correct handling of the percent sign in URIs.


====( 0.4.0 )====
2008-10-05

The distribution contains the documentation now, making it complete.

Lots of new documentation.

Minor, but many, changes in the syntax of command line options.  Basically, all parameters but files and directories are given using the --param=val style.

The directory for temporary files can be created automatically, if allowed.

New operator, &|, that combines dynamic bindings with priority to the second argument.

Pages can be grouped to have equal media boxes.  At the moment, the media box will be the smallest that contains the bounding boxes of all pages in the group.  See the non-pure function setbboxgroup for more details.

The document can be split into one output file per page, see the --split=mode option.

Improvements relating to PDF versions including a separate setting for whether to use transparency in the kernel, and not marking the output file with a higher version than what is implied by the PDF features is uses.

Additions and improvements to some of the standard extensions.

Bugfixes include:
-  Intersection of straight line segments.
-  Sometimes, functions were associated with the wrong environment.
-  Escaping the '\' in PDF strings.


====( 0.3.7 )====
2008-04-21

The previous version was broken.  This version has been verified by running "make distcheck".


====( 0.3.6 )====
2008-04-20

Lots of new documentation, including substantial work on structure, crosslinks, and formatting.  So far the HTML format has been in focus.

Procedure application is limited to certain scoping rules to ensure that the function abstraction is not broken.

Improved output to help finding errors i TeX label strings, and a bug with the --tmpdir feature was remedied.

Changed command line syntax for boolean options changed; no more --no-someopt, instead we use --someopt=no (the "no" has some synonyms).

New features of all kinds, ranging from additions to the scanner to new state types and functions.

Also new application examples in 3D, code optimizations, and bugfixes.


====( 0.3.5 )====
2007-12-06

The previous attempt to create a file for distribution failed.  This version is the second attempt.


====( 0.3.4 )====
2007-12-03

Bugfixes, including one in the computation of elementary paths.  There also used to be a problem (since 0.3.2) with running pdfLaTeX in a different directory than where the Shapes source is located, since the meaning of relative file locations must be changed when source code is moved.

This is the first version planned for (very limited) distribution using the new build process.


====( 0.3.3 )====
2007-11-21

Simple constants in the global environment were named back to their names before variables had to begin with lowercase letters.  For instance, rgb_RED changed back to RGB_RED.


====( 0.3.2 )====
2007-11-21

New ways to specify files, both on the command line and through environment variables.

Further improved build process, and minor additions to the documentation.


====( 0.3.1 )====
2007-11-05

Bugfixes required to make the project compile in the Cent environment.

More standardization.


====( 0.3.0 )====
2007-11-03

First version with most references to old project names removed.

Slowly changing to a more standardized way to compile things, for better compilance with standard make tools in the future.


====( 0.2.3 )====
2007-11-03

Upsampling has been added.  The interesting methods for upsampling only apply in 2D, but length-based upsampling is provided also in 3D.  Please note that there is no need to do upsample_inflections before doing upsample_bends, as this is done autimatically to ensure clear semantics.  The method upsample_balance samlpes the timewise midpoint of each segment, which I believe will make the speed equal in the incoming and outgoing side of the sample point.

Identifiers are again allowed to begin with uppercase letters.  Type names are prefixed with either a paragraph sign or a double slash.

This is planned to be the last version where anything "Drool" remains.


====( 0.2.2 )====
2007-06-05

The interpreter now makes another pass of the code, checking variable bindings, function borders, and other static aspects of the code.  Type checking will hopefully fit in here in the future.  The three passes are:
1) Scan and parse
2) Analyze
3) Evaluate

The error reporting mechanism has been revised so that the errors found during static analysis are collected in a list, rather than throwing just the first we detect and then abort.


====( 0.2.1 )====
2007-05-19

By now many feature examples have been compiled successfully, and the tests go through.

More importantly, the random number facility has been redesigned so that states are used where appropriate.  To make it easy to use states in folds, the kernel's list type has been enhanced with methods foldsl ("fold with state, left") and foldsr ("fold with state, right").  However, this was not quite necessary since the same functionality can be implemented as an extension, as was done in conssupport.drext, and used random.drool.

Among all bugs found lately, one was in the z-buffer.  Although it was fixed, I'm not at all convinced that transforms are handled correctly, nor that overlaps and line-surface intersections are determined correctly.


====( 0.2.0 )====
2007-04-24

This version marks the point where the two feature examples states.drool and values.drool compile.  This means that the program is getting useful again.  However, the great majority of the examples have not been updated, and it is expected that many bugs will be revealed in the process of updating them.

In other words, this version marks the beginning of the use of states and structures, but these features should be debugged and tested on the many available examples before being considered a true alternative to using the language as of version 0.1.1.


====( 0.1.2 )====

This version is to be used during the early phases of the transition from hot variables to temporary states.  One the program becomes useful again, the version number shall be incremented.


====( 0.1.1 )====
2007-01-02

Testing has been automated.  The tests are divided into two cathegories depending on whether it is the graphical or textual program output that is to be compared against a given output.  See the Makefile's in the ./test directory and its subdirectories to learn how to run the tests or add new tests.

The z-buffer idea has been postponed.  Instead, a z-sorter has been implemented.  It does not handle cyclic overlaps properly.

There are lots of bugfixes and small enhancements over the previous version.  One of the enhancements is the "[...]"-syntax for evaluated cuts along one argument.

This is planned to be the the last usable version with hot variables.


====( 0.1 )====
2006-12-12

First named version.

I'd say this is far too late for the introduction of a version number.  The reason not to make a named version has been that rather big changes in the language syntax have been expected.  However, these changes are still expected, but today I was really curious to know what binary I had installed, and this is what made me take this step.

To give an idea of how long this project has been running I'll mention two things.  First, the initial import of the project into subversion dates back to 2005-09-23.  Second, there's now 395 kB of zipped source code for the compiler.  In addition, there are many examples and language extension files.

There still not much at all of documentation.  Comments in the source are sparse, much too sparse.  A user's guide hsa been initiated, but the files have not yet entered the project repository.  There is no laguage definition either, but this is partly because the language is still expected to change substantially.

A few words about testing:  The testing is without structure so far.  I generate examples to test the features I'm currently working on, but I do not generate tests that can be checked automatically.  This probably says something about the quality of this version.  That I plan automatize testing soon does not make this version better.

The list of features that exist in this version is much too long for me to think of right now.  The first such a list I expect to create will be the user documentation, so until then the examples is as close as one gets.