Mike Gerwitz
00ff660008
This begins demonstrating that the root will be utilized for identifier lookup and indexing, as it was originally for TAME and is currently for the linker. This was _not_ the original plan---the plan was to have identifiers indexed only at the package level, at least until we need a global lookup for something else---but that plan was upended by how externs are currently handled. So, for now, we need a global scope. (Externs are resolved by the linker in such a way that _any_ package that happens to be imported transitively may resolve the import. This is a global environment, which I had hoped to get rid of, and which will need to eventually go away (possibly along with externs) to support loading multiple programs into the graph simultaneously for cross-program analysis.) This commit renames the base state for `AirAggregate` to emphasize the fact, especially when observing it in the `AirStack`, and changes `AirAggregateCtx::lookup_lexical_or_missing` to resolve from the _bottom_ of the stack upward, rather than reverse, to prove that the system still operates correctly with this change in place. The reason for this direction change is to simplify lookup in the most general case of non-local identifiers, which are almost all of them in practice---they'll be immediately resolved at the root once they're indexed. This can be done because I determined that I will _not_ support shadowing; rationale for that will come later, but TAME is intended to be a language suitable for non-programmer audiences as well. Note that identifiers will be resolved lexically within templates in TAMER, unlike TAME, which means that the expansion context will _not_ be considered when checking for shadowing, so templates will still be able to compose without a problem so long as they do not shadow in their definition context. (I'll have to consider how that affects template-generating templates later on, but that's an ambiguous construction in TAME today anyway.) This _does not_ yet index anything at the root where it wasn't already being indexed explicitly. DEV-13162 |
||
|---|---|---|
| bin | ||
| build-aux | ||
| core | ||
| design/tpl | ||
| doc | ||
| progtest | ||
| rater | ||
| src | ||
| tamer | ||
| test | ||
| tools | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| .rev-xmle | ||
| .rev-xmlo | ||
| COPYING | ||
| COPYING.FDL | ||
| HACKING | ||
| Makefile.am | ||
| README.md | ||
| RELEASES.md | ||
| VERSION.in | ||
| bootstrap | ||
| c1map.xsd | ||
| configure.ac | ||
| package-lock.json | ||
README.md
TAME
TAME is The Algebraic Metalanguage, a programming language and system of tools designed to aid in the development, understanding, and maintenance of systems performing numerous calculations on a complex graph of dependencies, conditions, and a large number of inputs.
This system was developed at Ryan Specialty Group (formerly LoVullo Associates) to handle the complexity of comparative insurance rating systems. It is a domain-specific language (DSL) that itself encourages, through the use of templates, the creation of sub-DSLs. TAME itself is at heart a calculator—processing only numerical input and output—driven by quantifiers as predicates. Calculations and quantifiers are written declaratively without concern for order of execution.
The system has powerful dependency resolution and data flow capabilities.
TAME consists of a macro processor (implementing a metalanguage), numerous compilers for various targets (JavaScript, HTML documentation and debugging environment, LaTeX, and others), linkers, and supporting tools. The input grammar is XML, and the majority of the project (including the macro processor, compilers, and linkers) is written in a combination of XSLT and Rust.
TAMER
Due to performance requirements, this project is currently being reimplemented in Rust. That project can be found in the tamer/ directory.
Documentation
Compiled documentation for the latest release is available via our GitLab mirror, which uses the same build pipeline as we do on our internal GitLab instance. Available formats are:
Getting Started
To get started, make sure Saxon version 9 or later is available and its path
set as SAXON_CP; that the path to hoxsl is set via HOXSL; and then run
the bootstrap script:
$ export SAXON_CP=/path/to/saxon9he.jar
$ export HOXSL=/path/to/hoxsl/root
$ ./boostrap
Running Test Cases
To run the test cases, invoke make check (or its alias, make test).
Testing Core Features
In order to run tests located at core/test/core/**, a supporting environment
is required. (e.g. mega rater). Inside a supporting rater, either check out a
submodule containing the core tests, or temporarily add them into the
submodule.
Build the core test suite summary page using:
$ make rater/core/test/core/suite.html
Visit the summary page in a web browser and click the Calculate Premium button. If all test cases pass, it will yield a value of $1.
Hacking
Information for TAME developers can be found in the file HACKING.
License
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.