|New entry |
We have released version 2.1.1 of Orc, a minor update. This release makes no language changes. The release does improve the Orc Eclipse plug-in and extends the standard library slightly. In addition, significant work has gone into improving the underlying implementation.
There are multiple ways to run Orc:
1. Use our Try Orc ( https://orc.csres.utexas.edu/tryorc.shtml ) feature to experiment with Orc in your Web browser.
2. Use the Orc plug-in for Eclipse, available as "Orc" on the Eclipse Marketplace. (In Eclipse, use the menu item Help > Eclipse Marketplace) If you already have the Orc plug-in for Eclipse installed, use the Check for Updates menu item to get the update.
3. Orc is also available as a standalone JAR which you can use to run programs on the command line. You can download the release archive from GitHub at https://github.com/orc-lang/orc/releases .
--The Orc Language Research Team
With the shutdown of Google Code Project Hosting, we have migrated to GitHub. This, of course, means that we have changed our version control system to git.
All of the Orc source repository, release files, and issues (including history of each) is now available at https://github.com/orc-lang/orc
Be sure to "star" the orc-lang/orc repo on GitHub.
Orc 2.0 is a new major revision of the Orc implementation. The core codebase has been rewritten in Scala, and the internal structure of the compiler and runtime have been altered and improved substantially.
The user-level surface language has also changed. Orc 2.0 is not backwards-compatible with previous versions of Orc. Here are the detailed release notes on the user-visible changes to the language. Guidance on how to modify programs written in the previous version of Orc to make them run under Orc 2.0 is on the UpgradingYourProgramToOrc2.0 page.
See our Downloads page for detailed instructions on how to download and use Orc within Eclipse, locally within your web browser, or from the command line.
- Support for records: record expressions, record types, record patterns, and record extension using +
- Function clauses may have arbitrary guard conditions.
- New web library section, with sites Browse, HTTP, ReadJSON, and WriteJSON
- New xml library section, with XML manipulation sites.
- Enhanced parse error messages.
- Enhanced compiler and runtime error messages, with links into the Orc Wiki.
- The .oil compiled representation of Orc programs now has a standard public format, given by orc.csres.utexas.edu/oil.xsd.
- Orc compiler and runtime support JSR 223.
- Orc 2.0 has a full Reference Manual.
- Added site IterableToStream to convert Java objects implementing Iterable to a more Orc-appropriate idiom.
- Any value with an apply member can be called; the call is forwarded to the apply member.
- Any value with an unapply member can be used in a call pattern; the match target is forwarded to the unapply member.
- def capsule is now def class.
- site is now import site.
- class is now import class.
- type is now import type for external types. Type aliases and datatypes remain unchanged.
- The three import declarations require the Java class name to be a quoted string.
- The comparison operators < and > are now <: and :>.
- if site is now Ift. Ift has a counterpart, Iff.
- IArray is now Table.
- Rtimer is now Rwait.
- Buffer is now Channel. BoundedBuffer is now BoundedChannel.
- "Nonblocking" sites, with the suffix 'nb', are now "definite" sites, with the suffix 'D'.
- Site names are now capitalized by convention. This has changed many sites in the standard library: Let, Print, Println, Error, Read, Write, Floor, Ceil, Random, URandom.
- Keywords are reserved. (Previously one could, for example, define a function named "stop".)
- Orc identifiers may now use Unicode letters.
- Fixed bugs in Floor and Ceil.
- Arrays no longer have any methods. They have one field, length. For slice, use the new function sliceArray.
- Arrays no longer pattern match as lists. Use arrayToList.
- Descendants of Iterable no longer pattern match as lists. Use iterableToList.
- All Orc programs and includes are interpreted using the UTF-8 character encoding.
- Tracing facilities have been removed.
- Experimental support for Orc exception handling syntax has been removed.
- Special treatment of interaction between if then else and >> in parser has been removed.
- if then without else is no longer supported. Always use if then else.
- Equality (=x) pattern is gone. Use a guard on the clause instead.
- Special treatment of newlines has been removed. Ambiguous syntax can be eliminated with the insertion of signal >>.
- Curried definition of functions, lambdas, and function types are no longer allowed. Expand these explicitly as chained lambdas instead.
- Record has been removed; use primitive records instead.
- Set and Map have been removed; use Scala or Java counterparts instead.
- cat has been removed, use + on strings instead.
- Clock has been removed, use Rclock instead.
- Ltimer and withLtimer have been removed.
- Apply has been removed.
- Thread has been removed.
- () as a synonym for signal has been removed.
- All uses of and dependencies on Kilim have been removed.
This is a maintenance release, with no significant new non-experimental features.
- Allow Orc to load include files from the filesystem: use the -I option to specify the include path.
- Experimental support for "isolated" actors which are garbage collected when blocked permanently.
- Adding Record site for creating record-like objects.
- Demo of a compiler backend which translates OIL into Orc-like source text.
- Adding -oil option to Orc compiler to output Oil.
- Report parse errors in include files more clearly. Report a few kinds of parse errors (where backtracking is unwarranted) more clearly.
- Type assertions are now available; write :!: T to assert T as the type of an expression or the return type of a definition.
- Detect when a program is blocked permanently (sometimes) and halt execution.
- New semantics for nested logical timers: a parent timer can advance when its children are quiescent (as opposed to halted).
- Moving lib.data to lib.state.
- All non-Kilim Java methods and constructors should evaluate in the "sites" thread.
- Publish pattern (!p) has been removed from the language completely.
- Before/After events no longer appear in traces. A future version will restore this functionality.
- Fix parsing of floating point. Bug found by Sydney.
- Fix Eclipse 3.1 compilation issues.
- Fixing OIL->XML serialization error with Orc field values.
- Fixing parse error for "type x = lambda () :: ..."
We recently completed a new paper to appear in Proceedings of FMOODS/FORTE 2009, where Prof. Misra is the invited speaker. While most of the material in the paper has already appeared in an expanded form in the user guide, this paper serves as a slightly more compact introduction to the Orc language and its use.
The goal of this release is to get important bugfixes and enhancements released before we embark on a significant refactoring of the engine to make it more extensible.
Highlights of this release:
- Improved prototype type checker and type annotation syntax: now actually usable for most real programs.
- withLock, rangeBy, altMap, joinMap, seqMap functions added to stdlib.
- types which can be tested for structural equality are registered in a set which can be augmented by user libraries.
- Prototype runtime (dag, token, etc) support for transactions.
- Prototype implementation of nestable and independent logical timers.
- Set, Map, and Array support site call notation for reading and
writing elements, e.g. "a(3) := 4"
- Compiler service works correctly.
- Web service examples work correctly.
- Compiles and runs under JRE 1.6 (Java SE 6).
- The "unguarded recursion checker" handles semicolon correctly.
- Fix bugs with foldr1 and range in stdlib.
- Fix bug with using immutable values as keys in Map and Set.
- Publish patterns (">!x>") no longer supported; use " >x> ( x | ... )" instead.
- Stdlib "por" and "pand" take lists instead of two arguments.
- "sequence" stdlib function renamed to "seq".
- Left and Right datatypes no longer included in stdlib.
- Tokens are no longer pooled; speed benefit is not significant enough to justify memory wastage.
- Failed pattern matching in definitions causes an error message.
Highlights of this release:
- New syntactic sugar "x?" and "x:=y" for reference reads and writes.
- Operators can be written in prefix form (or unapplied) using parentheses: "(+)" is equivalent to "lambda (a,b) = a+b".
- New "type" declaration for declaring algebraic data type constructors.
- Any combinator is allowed unparenthesized within if/then/else.
- Allow apostrophe in var names.
- Allow nested comments.
- Newline-sensitivity avoids ambiguity about where expressions end.
- Equality operator "=" now obeys substitutability principle.
- New semantics for semicolon operator: in "a ; b", "b" runs only if "a" fails without publishing any values.
- Java fields can be accessed with the dot operator.
- Standard library organized, documented, and expanded with many more useful sites and definitions.
- Experimental support for "doc" tags ala javadoc, translated into docbook syntax by a special parser.
- Enforceable limits on recursive stack depth and logical threads.
- A closure only keeps variables used in the closure live, for garbage collection purposes.
- Definitions are organized into mutually-recursive groups to keep environments small and avoid false depenendencies on futures introduced by the pruning combinator.
I'm pleased to announce the release of a new version, timed to coincide with the initial version of the new userguide. Some of the highlights of this release:
- New syntactic sugar for if/then/else: if X then Y else Z <=> if(b) >> Y | if(~b) >> Z <b< X
- New syntax "signal" as a (prefered) synonym for "()" and "let()"
- "." may now be used to the right of any basic expression (not just a variable or call) so for example "3.toString()" should work.
- Revised semantics for logical timers: logical time is not allowed to proceed as long as there are pending calls to any other sites. This semantics, while easier to reason about, makes correct programs harder to write, so we are still investigating alternatives.
- Fixed semicolon operator so that the left expression is recognized as dead when all tokens have left it (even if they are not dead yet).
- Support for constructing and using Java arrays, including primitive arrays.
- Allow list deconstructors to be used on strings (like Haskell).
- Java implicit unboxing and conversions work in many more cases.
- Unguarded direct recursion is detected as a compile-time error.
- Support for recording traces of programs, to be used for debugging and profiling tools current under development
- Regression tests based on JUnit added. We can now test all of the example programs for correct behavior (ignoring non-determinism) as well as parsability.
- Huge increase in efficiency of Java integration