2b146e886b
Migrate to latest MPS 2026.1 EAP
2026-04-24 11:22:20 +02:00
53ab46fba7
Apply migrations and rebuild
2025-11-03 12:33:34 +01:00
1a1cb13621
Apply migrations from 251
2025-04-09 11:34:06 +02:00
17dd2a6c01
Appply migrations from MPS 243 branch
2024-12-11 11:57:18 +01:00
286f20e70a
Untangle dependencies and rebuild project
2024-08-29 13:09:49 +02:00
4ce08f4b99
Refactor project structure and reduce the number of modules
2024-07-04 18:17:56 +02:00
0776351977
Ran CleanStubForeignMethodIds migration
2024-01-23 16:33:23 +01:00
3cf666e633
Apply migrations and make project
2023-07-31 12:57:24 +02:00
6a849f82f2
Apply migrations and rebuild project
2023-06-12 12:01:02 +02:00
d531c6a5ad
Run Migration Assistant
2023-02-22 13:52:02 +01:00
ad3ea9d63d
Apply all migrations from 2022.2
2022-11-21 11:25:13 +01:00
4e70300ea7
Update language imports
2021-11-24 16:22:17 +01:00
2d52921561
Fix and optimize dependencies
2021-09-22 17:08:25 +02:00
9527a097b8
Migrate to the latest MPS release, apply migrations
2021-06-18 18:41:01 +02:00
ff6b5ec6ae
Apply migrations and rebuild project
2021-04-14 13:19:50 +02:00
7fe5a5ad7a
Auto-updated files after migrating to MPS 2021.1 EAP
2021-02-04 12:26:59 +01:00
62e8e7d013
Switch to MPS 2020.3 release.
2021-01-08 11:00:02 +01:00
936190bca9
Apply migrations.
2020-07-11 15:13:08 +02:00
e2aa9fd53f
Fix LogicalItemExpression contained in ExpressionItem issue, provide migration.
...
It's possible to a cycle b/w the two concepts, which is totally unnecessary.
This provides the means for detecting and fixing this problem.
2020-07-11 14:47:53 +02:00
14780b5561
Apply automatic migrations.
2020-05-09 15:04:25 +02:00
a0bc96b3e0
Move all concepts related to term to j.m.coderules.
2020-04-13 17:58:34 +02:00
a1c98b5bf0
Apply all outstanding migrations.
2020-04-13 17:58:33 +02:00
4845e120e9
Introduce termlist type, rename multilogical type to logical[].
2020-04-13 17:58:33 +02:00
e8a19249e6
Migration to replace spliced LogicalItemExpression on a list node.
...
Usually one uses Splice with LogicalItemExpression wrapping a logical variable.
Using LogicalDataForm wrapping same variable makes Splice unnecessary.
In order to keep code readable these are wrapped again in a cons list.
In general, one should avoid using bare LogicalDataForm, as these are
indistiguishable from normal LogicalVariable.
2020-04-13 17:58:33 +02:00
065aac819c
Introduce construct to directly insert term constructor in data form.
...
Usually one uses Splice with LogicalItemExpression wrapping a constructor.
The new TermConstructorDataForm provides a shortcut.
2020-04-13 17:58:33 +02:00
73beb56834
Introduce ConsListNode to replace a deprecated concept. Migration.
...
Prefer aggregation over inheritance: ListNodeCons extending ListNode
is not a good design.
Also drop LogicalUnrapContext, as it has no real use.
2020-04-13 17:58:33 +02:00
f2bb87e1b0
Apply migration to replace deprecated concept.
2020-02-26 15:03:31 +01:00
c064972266
Deprecate obsolete concept, provide migration. Minor editor fixes.
...
ExpressionLogicalVariable is replaced with ExpressionItem wrapping
the same expression.
Fixes ensure correct application of transformations.
Late expression can't be used as "placeholder" logical item.
2020-02-26 15:01:29 +01:00
7ba7c983cb
Apply migration to use logical variable ref expression.
2020-02-24 22:57:05 +01:00
630fd33629
Introduce logical var reference expression.
...
This expression is to be used in those rare cases
when a logical var is to be passed to an external method.
Not available within EvaluationSetting (new marker interface).
Normally logical variable (as an instance of LogicalItem)
is only to be used within a logical context.
Logical item value expr only to contain a logical variable.
2020-02-24 22:56:54 +01:00
796ad9ad2c
Apply migration to drop ValueOfExpression.
2020-02-12 12:26:09 +01:00
0d7316adf4
Introduce LogicalItemValueExpr, deprecate ValueOfExpr, migration.
...
LogicalItemValueExpression is to play the same role as valueOf(logical)
within an instance of EvaluationSubject.
LogicalItemExpression is to represent the logical variable itself.
2020-02-12 12:18:30 +01:00
3f51c1e5c1
Apply migration that replaces empty logical type with term type.
2020-02-05 12:34:20 +01:00
58a1cf16fe
Introduce TermType (term) to be represented as "DataForm" in runtime. Migration to specify term type where expected.
2020-02-05 12:24:40 +01:00
391c9053b5
Apply migrations after switch to MPS 193. Regenerate project.
2020-02-03 11:24:22 +01:00
cdfe1f2c0c
Update language version after migrations from mps.logic lang
2019-09-11 13:24:02 +03:00
7242e832b1
Upd mps.logic lang version
2019-09-11 13:24:02 +03:00
d786ff43b9
Re-save all models, language name updated in .mpl files.
2019-08-20 23:11:19 +02:00
3a48c47880
Migration: "update versions in descriptors".
2019-07-30 11:49:26 +02:00
66c9222a95
Run migrations with MPS 2019.2 EAP3.
2019-07-26 17:27:18 +02:00
79b08c6f83
Revert "Apply migrations from EAP3 and rebuild project."
...
This reverts commit 9c5bf858c3
2019-07-26 15:30:30 +02:00
9c5bf858c3
Apply migrations from EAP3 and rebuild project.
2019-07-19 12:28:27 +02:00
cd37daaa07
Apply migrations after switching to the latest EAP build of MPS.
2019-06-07 09:16:21 +02:00
17ed4642ae
Apply all available automatic migrations.
2019-06-05 16:16:00 +02:00
19ce84f7ef
Switch to 2018.3 RC. Apply all migrations.
2018-11-28 16:48:59 +01:00
c7cc97fffb
Rename reporting runtim solution.
2018-07-21 13:29:40 +02:00
ea9919f38a
Bring the hierarchy of DataForm concepts in line with the runtime.
...
Merge DataForm constructors into logic language.
Repackaging logic runtime.
Drop obsolete code.
2018-07-21 13:29:22 +02:00
79c02d2b00
Cleaning up dependencies in an attempt to produce a workable build.xml that doesn't break gradle.
2018-07-14 17:22:14 +02:00
92c6ba3e12
Restructuring the project: consolidate code, moving samples away.
2018-07-14 17:22:07 +02:00
Fedor Isakov