'bind' as a declarative statement

This commit is contained in:
Araq
2011-10-10 02:04:15 +02:00
parent c138cc36b4
commit 51e01879ba
18 changed files with 204 additions and 93 deletions

View File

@@ -38,6 +38,7 @@ Changes affecting backwards compatibility
- The ``pure`` pragma for procs has been renamed to ``noStackFrame``.
- The threading API has been completely redesigned.
- The ``unidecode`` module is now thread-safe and its interface has changed.
- The ``bind`` expression is deprecated, use a ``bind`` declaration instead.
Language Additions
@@ -55,6 +56,8 @@ Language Additions
- There is a new user-definable syntactic construct ``a{i, ...}``
that has no semantics yet for built-in types and so can be overloaded to your
heart's content.
- ``bind`` (used for symbol binding in templates and generics) is now a
declarative statement.
Compiler Additions

View File

@@ -31,6 +31,13 @@ You have to find out for yourself. If you don't find a tongue-in-cheek
interpretation you will have to look harder.
Why yet another programming language?
-------------------------------------
Nimrod is one of the very few *programmable* strongly typed languages, and
one of the even fewer that will produce native binaries that require no
runtime or interpreter.
How is Nimrod licensed?
-----------------------