You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While we have the package system, library system, and many packages available for Muddle 55, Muddle 56 is only the bare interpreter. While packages created in Muddle 55 (for which we have a compiler and assembler) run in Muddle 56, we haven't yet been able to get Muddle 56 dumped such that it can load libraries and packages without manual intervention. This manual intervention sometimes is very tricky to get right. Consequently, Muddle 56 (which is TENEX Muddle 106 back-ported to ITS), is not really usable as is.
Ideally, we would be able to load NEWMUD > into a fresh Muddle 56 interpreter and PDUMP the image, to get a Muddle 56 interpreter that could leverage the package system, library system, and debugging tools.
The text was updated successfully, but these errors were encountered:
While we have the package system, library system, and many packages available for Muddle 55, Muddle 56 is only the bare interpreter. While packages created in Muddle 55 (for which we have a compiler and assembler) run in Muddle 56, we haven't yet been able to get Muddle 56 dumped such that it can load libraries and packages without manual intervention. This manual intervention sometimes is very tricky to get right. Consequently, Muddle 56 (which is TENEX Muddle 106 back-ported to ITS), is not really usable as is.
Ideally, we would be able to load NEWMUD > into a fresh Muddle 56 interpreter and PDUMP the image, to get a Muddle 56 interpreter that could leverage the package system, library system, and debugging tools.
The text was updated successfully, but these errors were encountered: