POSITION math update/question

[pixel...@gmail.com]

I've added a function to add POSITIONS but I also noted that ADD was one of the "Changetran"  functions listen in the Manual.

I wasn't sure if this would be applicable to what I want to do.
Essentially, I'd like to implement a small file of these kinds of transformations (especially variadic/spread forms so I can treat multiple POSITIONS as 2D geometry vectors. - VERY handy.)

So my questions are these:
1. Should I instead be using the "Changetran" style functions? (I'd be looking to implement ALL geometric transforms as most calls to POSITION were manually fiddling with their fields each and every time.

2. If so, it seems new Changetran symbols would be needed for all standard transformations...

3. I believe recalling InterLisp doesn't have formal packages. How do I ship this such that others can use it? (Style, location, common calling conventions etc).

I really feel the POSITION record type needs some work to make them more powerful. Currently they're pretty anemic and people keep inventing the wheel to work with them. (Unless using the tools mentioned last Wednesday I've missed something).

I'll include a picture of the POSITION definition and also my new function.
InterLisp spread functions are not exactly pleasant. I do miss some modern &rest or . args form from other Lisps. Let me know if there is a better way than what I've done per the Dinfo manual with ARG.

PS, if you want me posting questions in a particular place rather than here point me there and I will so others can learn.

Thanks for your time, as always!

[Paolo Amoroso]

Concerning namespaces, the function names of Interlisp applications or subsystems usually add a prefix such as TB. for the Table Browser (e.g. TB.MAKE.BROWSER) and NCP. for NoteCards's programmer interface (e.g. NCP.CreateNoteFile).

--
You received this message because you are subscribed to the Google Groups "Medley Interlisp core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lispcore+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/lispcore/ff2e51f6-90c1-4e17-acb6-331b78b42e51n%40googlegroups.com.

--

Paolo Amoroso | Blog | Mastodon

[Larry Masinter]

Where to post:

Posting technical discussions to the "Discussions"  section on GitHub https://github.com/orgs/Interlisp/discussions has the slight advantage that it hopefully will contain the discussion to be on topic and more findable. Theoretical.  

But there are some drawbacks (if you want to see new discussions you have to sign up to watch) and other considerations (the 'lispcore' group is set up to avoid spam by requiring moderator approval for posts from non-members.

Style issues:

I think Interlisp users had a wide variety of style principles and there wasn't consensus. So you'll find a variety of styles in the Medley sources.

Some Interlisp styles were led by performance issues that may or may not be relevant today.

My suggestion is to take the challenge of writing your POSITION hacking in different styles (Interlisp and Common Lisp) and comparing the two.

--

 https://LarryMasinter.net  https://interlisp.org