use foreign aeon for foreign mark definitions

This commit is contained in:
Philip Monk 2019-01-13 23:46:21 -08:00
parent b1861d4bc7
commit ea0f233572
No known key found for this signature in database
GPG Key ID: B66E1F02604E44EC
2 changed files with 5 additions and 2 deletions

View File

@ -631,6 +631,7 @@
:: translate other cases to dates
::
=/ aey (case-to-aeon:ze case)
:: ~& [%case-to-date aey let.dom our her syd case]
?~ aey `@da`0
?: =(0 u.aey) `@da`0
t:(aeon-to-yaki:ze u.aey)
@ -3170,7 +3171,9 @@
:* hen %pass
=+ (cat 3 %diff- nam)
[%merge (scot %p p.bob) q.bob (scot %p p.ali) q.ali - ~]
%f %build live=%.n %pin (case-to-date r.oth) %list
%f %build live=%.n %pin
(case-to-date:((de our now hen ruf) p.oth q.oth) r.oth)
%list
^- (list schematic:ford)
%+ murn ~(tap by q.bas.dat)
|= {pax/path lob/lobe}

View File

@ -13,7 +13,7 @@
::
:: We call the date in the definition of a build the "formal date" to
:: distinguish it from the time at which the build was performed.
::
:: Each build is referentially transparent with respect to its formal date:
:: ask to run that function on the namespace and a particular formal date,
:: and Ford will always produce the same result.