Mike Gerwitz
0b9e91b936
This cleanup is an interesting one, because I think the present me may disagree with the past me. The use of generics here to compose the parser from smaller parsers was due to how I wrote my object-oriented code in other languages: where a class was an independently tested unit. I was trying to reproduce the same here, utilizing generics in the same way that one would use compoisition via object constructors in other languages. But it's been a long time since then, and I've come to settle on different standards in Rust. The components of `XmloReader` really are just implementation details. As I find myself about to want to modify its behavior, I don't _want_ to compose `XmloReader` from _different_ parsers; that may result in an invalid parse. There's one correct way to parse an xmlo file. If I want to parse the file differently, then `XmloReader` ought to expose a way of doing so. This is more rigid, but that rigidity buys us confidence that the system has been explicitly designed to support those operations. And that confidence gives us peace of mind knowing that the system won't compose in ways that we don't intend for it to. Of course, I _could_ design the system to compose in generic ways. But that's an over-generalization that I don't think will be helpful; it's not only a greater cognitive burden, but it's also a lot more work to ensure that invariants are properly upheld and to design an API that will ensure that parsing is always correct. It's simply not worth it. So, this makes `XmloReader` consistent with other parsers now, like `AirAggregate` and nir::parse (ele_parse). This prepares for a change to make `XmloReader` configurable to avoid loading fragments from object files, since that's very wasteful for `tamec`. 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.