New entry
12-Apr-2009 19:46
Google Code, Subversion, and v0.9.8#

This weekend the project made some major administrative changes.

  • Most importantly, we changed project hosting from SourceForge to Google Code. All SourceForge services are now deactivated, including CVS and hosting of old releases. Old releases are available in source code form via version control; if there is demand for pre-packaged binaries of old releases, I can put them on Google Code.
  • We changed version control systems from CVS to Subversion. Google Code has the SVN repository information. For more details on the switch, see MigratingToSvn.
  • We changed our source code license to the "New" BSD license. The new license has more liberal terms than our previous license (which forbade commercial use) so this should not affect anybody already using our code.
  • We cleaned up our library dependencies to ensure we are complying with licensing terms for all bundled third-party libraries.
  • We released version 0.9.8, primarily to make the binaries available under the new license.
07-Mar-2009 11:49
News Blog Added#

This is the first official entry in the Orc news blog. The goal of this blog is to provide a record of activity on the project, such as releases and important bugfixes. Just so the blog doesn't look embarassingly empty, I have posted some old release notes, back-dated.

Some recent documentation activity:

  • There is now a community-maintained FAQ. Hopefully this will grow as we get more users asking questions.
  • The User Guide now includes a fairly comprehensive chapter on implementing sites to be used by Orc programs.

I'd also like to report a few enhancements to the development version of Orc (available via CVS):

  • The standalone compiler has a new option -oil which allows you to generate an XML representation of a desugared AST, called OIL (Orc Intermediate Language). This should be helpful for external analysis tools and alternate implementations of the engine, so they don't have to implement their own parser and compiler frontend. You can learn about the structure of OIL from the Javadoc. To generate a copy of the schema, run the class orc.ast.oil.Oil (bundled with the compiler JAR).
  • For people interested in developing their own compiler backends who don't want to parse OIL XML, there is a demonstration of how to invoke the compiler frontend and translate OIL to an arbitrary intermediate representation: https://orc.cvs.sourceforge.net/viewvc/orc/OrcJava/src/orc/BackendDemo.java?view=markup

Add new attachment

Only authorized users are allowed to upload new attachments.
« This page (revision-4) was last changed on 09-Jun-2016 15:41 by John Thywissen