clean retranscript of AVTests

[masinter]

replaces PR #17 to only include the @skaisler1 test handler

[skaisler1]

Larry: Thanks very much for helping! I would never have detected this. so, questions: 1. Should the distribution of Medley now include the New Interlisp Readtable as default? I would suggest it should. I had not seen a notice of this. 2. Did you make a change to the LOOPS Source code, so that I should download a new version? 3.We need to com up with a mechanism for alerting users about such changes as they occur. I am sure that every release of Medley and, eventually, of LOOPS and other code, that changes will be made and they need to be posted somewhere for people to read. We should not require them, I don't think, to go to GitHub to find out what is changing. Steve K.

…

On 02/22/2024 10:19 PM EST Larry Masinter ***@***.***> wrote: replaces PR #17 #17 to only include the @skaisler1 https://github.com/skaisler1 test handler --------------------------------------------- You can view, comment on, or merge this pull request online at: #18 Commit Summary * 08cf35f 08cf35f clean retranscript of AVTests File Changes (2 files https://github.com/Interlisp/loops/pull/18/files) * A test/medley/LOOPSTEST https://github.com/Interlisp/loops/pull/18/files#diff-6fe183452b95569b4e6f171c70b75cc4eb107a320269b5057f6a2396f6d54b87 (264) * A test/medley/LOOPSTEST.DFASL https://github.com/Interlisp/loops/pull/18/files#diff-c22f7a7917e5ba189562ea8048b911226b64c0d681c73fb673374b41b0ad7ade (0) Patch Links: * https://github.com/Interlisp/loops/pull/18.patch * https://github.com/Interlisp/loops/pull/18.diff — Reply to this email directly, view it on GitHub #18, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJMVT23ZIJJIX5KZODOGEC3YVADFTAVCNFSM6AAAAABDWBJY5GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE2TAMRZHAYDOMA. You are receiving this because you were mentioned.Message ID: ***@***.***>

[masinter]

I added as separate commits the change from .DCOMs.
I also added an experimental feature of taking the scripts of things to try to be a
BKSYSBUFOBJ (from the DEMO commit in Medley). Try it! (MAKE-TEDIT-TEST AVTEST1)

[masinter]

1. Should the distribution of Medley now include the New Interlisp Readtable as default?

The change of the INTERLISP readtable compared to OLD-INTERLISP-T and OLD-INTERLISP-FILE happened quite a long time ago (in the 90s at the latest). The OLD-INTERLISP readtables don't have single-quote 'X as an alternative to (QUOTE X) and don't treat : as a package delimiter.

The "new INTERLISP readtable" isn't new.

2. Did you make a change to the LOOPS Source code, so that I should download a new version?

The proposal in this PR (#17) does not include any changes to the LOOPS source code, but has some changes to the LOOPS/test folder in the Loops repository. My suggestion is you download, try, review and then approve this PR for merging.

3.We need to com up with a mechanism for alerting users about such changes as they occur. I am sure that every release of Medley and, eventually, of LOOPS and other code, that changes will be made and they need to be posted somewhere for people to read. We should not require them, I don't think, to go to GitHub to find out what is changing. Steve K.

This function was the purpose of the "Release notes" to be a summary of things that have changed.

The Medley Release Notes were in the middle of being updated from Medley 2 to Medley 3.5.
Yes, we need more better introductory text.

That's a Documentation Issue.

[skaisler1]

Larry: It seems then that the Loops example in the LRM may ave been written before the readtable change.Would probably need to go through PARC memos, etc to determine when. Thus, it seems to be a historical issue, but not one to alert readers, although in addition to Release Notes, we might need to have a Historical notes that captures the readtable change to inforom users who might have pre-199x (say) Lisp or LOOPS code. I have downloaded and used your solutions. Many thanks and am includiing them in Medley LOOPS:Basic System. I am not sure if I have the ability to approve PRs. Steve K.

…

On 02/23/2024 9:28 PM EST Larry Masinter ***@***.***> wrote: > 1. Should the distribution of Medley now include the New Interlisp Readtable as default? > The change of the INTERLISP readtable compared to OLD-INTERLISP-T and OLD-INTERLISP-FILE happened quite a long time ago (in the 90s at the latest). The OLD-INTERLISP readtables don't have single-quote 'X as an alternative to (QUOTE X) and don't treat : as a package delimiter. The "new INTERLISP readtable" isn't new. > 1. Did you make a change to the LOOPS Source code, so that I should download a new version? > The proposal in this PR (#17 #17) does not include any changes to the LOOPS source code, but has some changes to the LOOPS/test folder in the Loops repository. My suggestion is you download, try, review and then approve this PR for merging. > > 3.We need to com up with a mechanism for alerting users about such changes as they occur. I am sure that every release of Medley and, eventually, of LOOPS and other code, that changes will be made and they need to be posted somewhere for people to read. We should not require them, I don't think, to go to GitHub to find out what is changing. Steve K. > This function was the purpose of the "Release notes" to be a summary of things that have changed. The Medley Release Notes were in the middle of being updated from Medley 2 to Medley 3.5. Yes, we need more better introductory text. That's a Documentation Issue. — Reply to this email directly, view it on GitHub #18 (comment), or unsubscribe https://github.com/notifications/unsubscribe-auth/AJMVT26AUBAVV6OAR7CWEVDYVFF4PAVCNFSM6AAAAABDWBJY5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRSGIZDCMJSGE. You are receiving this because you were mentioned.Message ID: ***@***.***>

[masinter]

https://interlisp.org/pub-pdfs/all-medley.pdf#page=1515 Page 1515 explains.