Specifying framework constraints with FCL
Bibliographic record
Abstract
Object-oriented application frameworks are often misused because application developers do not know how the original framework designers intend their frameworks to be used. The goal of Framework Constraint Language (FCL) is to help detect errors in framework usage. FCL captures the intended usage of frameworks through framework constraints that describe the syntactic structures that frameworks impose on the code of framework-based applications. Framework constraints can be regarded as framework-specific typing rules conveyed by the FCL specifications and enforced by techniques analogous to those of conventional type checking. In essence, FCL is a first-order logic of the syntactic structure of programs. The feasibility and expressiveness of FCL have been evaluated by applying it to parts of frameworks, such as MFC (Microsoft Foundation Classes), and design rules such as Law of Demeter. The current version of the FCL language and associated checker is targeted at C++ frameworks.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.010 | 0.035 |
| Meta-epidemiology (narrow) | 0.002 | 0.003 |
| Meta-epidemiology (broad) | 0.002 | 0.004 |
| Bibliometrics | 0.005 | 0.003 |
| Science and technology studies | 0.002 | 0.005 |
| Scholarly communication | 0.008 | 0.009 |
| Open science | 0.005 | 0.006 |
| Research integrity | 0.003 | 0.004 |
| Insufficient payload (model declined to judge) | 0.014 | 0.003 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".