techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.6K
active users

#clos

0 posts0 participants0 posts today
Vassil Nikolov<p>[AMOP]<br><span class="h-card" translate="no"><a href="https://mathstodon.xyz/@dougmerritt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dougmerritt</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@weekend_editor" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>weekend_editor</span></a></span> <span class="h-card" translate="no"><a href="https://universeodon.com/@sigue" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sigue</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@abuseofnotation" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>abuseofnotation</span></a></span> <span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span></p><p>Right now I'm thinking that the real value of _The Art of the Metaobject Protocol_ is showing one way to do metaprogramming, and object-oriented programming is merely a demonstration domain.</p><p>Of course, what begat AMOP was a desire for an approach that can cover a large part of the OOP language design space, not just one point in that space, in order to be attractive to different schools of thought.</p><p><a href="https://ieji.de/tags/AMOP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AMOP</span></a><br><a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a><br><a href="https://ieji.de/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a></p>
Vassil Nikolov<p><span class="h-card" translate="no"><a href="https://mathstodon.xyz/@dougmerritt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dougmerritt</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@weekend_editor" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>weekend_editor</span></a></span> <span class="h-card" translate="no"><a href="https://universeodon.com/@sigue" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sigue</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@abuseofnotation" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>abuseofnotation</span></a></span> <span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span></p><p>&gt; no one else has been mentioning (so far as I've noticed) "The Art of the Metaobject Protocol"</p><p>Not in this thread.<br>Indeed, this book is a tour de force (et de magique).</p><p>&gt; uncertain that the topic deserved such a deep analysis</p><p>The topic—maybe, maybe not, but the book is really about the metatopic, i.e. about metaprogramming, if I may abuse this prefix.<br>(I know this ought to be formulated more carefully.)</p><p><a href="https://ieji.de/tags/AMOP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AMOP</span></a><br><a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a><br><a href="https://ieji.de/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a></p>
Vassil Nikolov<p><span class="h-card" translate="no"><a href="https://mathstodon.xyz/@weekend_editor" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>weekend_editor</span></a></span> <span class="h-card" translate="no"><a href="https://universeodon.com/@sigue" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sigue</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@dougmerritt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dougmerritt</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@abuseofnotation" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>abuseofnotation</span></a></span> <span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span></p><p>&gt; (call-next-method) is a procedural way to do this, costing an extra function call at runtime, but obviating the need for weird compilation.</p><p>And that is the costs-of-lisp-implementation consideration.</p><p>The other one is the program design consideration (including the costs of program modification), which often leads me to prefer a declarative style, but that is my point of view, there are always tradeoffs, etc.</p><p><a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a><br><a href="https://ieji.de/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a></p>
Vassil Nikolov<p><span class="h-card" translate="no"><a href="https://mathstodon.xyz/@weekend_editor" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>weekend_editor</span></a></span> <span class="h-card" translate="no"><a href="https://universeodon.com/@sigue" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sigue</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@dougmerritt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dougmerritt</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@abuseofnotation" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>abuseofnotation</span></a></span> <span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span></p><p>P.S.<br>If I recall correctly, freezing a set of class and generic function definitions (including the methods) precludes some operations later, like redefining a class at run time, but I don't know if this is related to your question.<br>Again, don't trust me.</p><p><a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a><br><a href="https://ieji.de/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a></p>
Vassil Nikolov<p><span class="h-card" translate="no"><a href="https://mathstodon.xyz/@weekend_editor" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>weekend_editor</span></a></span> <span class="h-card" translate="no"><a href="https://universeodon.com/@sigue" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sigue</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@dougmerritt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dougmerritt</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@abuseofnotation" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>abuseofnotation</span></a></span> <span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span></p><p>&gt; a CLOS equivalent to (compile-flavor-methods), that compiles all those combined methods so they don't have to be done at load or run time?</p><p>Not in the (full¹) CLOS specification.<br>Speaking from uncertain memory, check it if it's important.<br>_________<br>¹ Including the parts not in the ANSI standard.</p><p>I have a very vague and insufficient memory of a non-Flavors implementation that provides something like that.</p><p><a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a><br><a href="https://ieji.de/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a></p>
Vassil Nikolov<p><span class="h-card" translate="no"><a href="https://universeodon.com/@sigue" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sigue</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@dougmerritt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dougmerritt</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@abuseofnotation" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>abuseofnotation</span></a></span> <span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span></p><p>&lt;"&gt;<br>I think the core feature is call-next-method, which can effectively be used to simulate around/before/after? (Not 100% sure it's an exact match.)<br>&lt;/"&gt;</p><p>Rather, the "before/after/around" approach is declarative, the `call-next-method' approach is procedural.<br>I can't recall a citation; I think this is even stated in the specification.</p><p>I'm afraid I'll leave a comparative analysis of the two approaches for another day 🙂.</p><p><a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a><br><a href="https://ieji.de/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a></p>
Vassil Nikolov<p><span class="h-card" translate="no"><a href="https://mathstodon.xyz/@dougmerritt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dougmerritt</span></a></span> <span class="h-card" translate="no"><a href="https://mathstodon.xyz/@abuseofnotation" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>abuseofnotation</span></a></span> <span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span> <span class="h-card" translate="no"><a href="https://universeodon.com/@sigue" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sigue</span></a></span></p><p>&gt; since it came up, how many CLOS features do you need?</p><p>You are right to ask.<br>Off the top of my head, I've needed<br>multiple inheritance,<br>multiple dispatch,<br>"before" and "after" methods.<br>Maybe I did something with method combination once or twice, but let's not count this if I can't recall properly.<br>But I am not a serious ("heavy-duty") <a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a> user.</p><p>If this counts, in other languages I have missed capabilities to customize object initialization.</p>
Vassil Nikolov<p>[Red Daly's Parenscript Object System, simplified-CLOS-like.]</p><p><span class="h-card" translate="no"><a href="https://mathstodon.xyz/@abuseofnotation" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>abuseofnotation</span></a></span> <span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span> <span class="h-card" translate="no"><a href="https://universeodon.com/@sigue" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sigue</span></a></span> </p><p>Thank you, that is impressive.<br>From Stanford.<br>Regrettably, I don't have the time to find out the extent of simplification.</p><p><a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a><br><a href="https://ieji.de/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a><br><a href="https://ieji.de/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JavaScript</span></a><br><a href="https://ieji.de/tags/Parenscript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Parenscript</span></a></p>
Vassil Nikolov<p>[Local generic functions.]</p><p><span class="h-card" translate="no"><a href="https://universeodon.com/@sigue" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sigue</span></a></span> <span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span></p><p>In fact, `generic-flet' was proposed and not adopted.</p><p>&lt;<a href="http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Issues/iss181.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">http://www.</span><span class="ellipsis">ai.mit.edu/projects/iiip/doc/C</span><span class="invisible">ommonLISP/HyperSpec/Issues/iss181.html</span></a>&gt;</p><p>I am glad you found a bug 🙂.</p><p><a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a><br><a href="https://ieji.de/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a></p>
Vassil Nikolov<p>[CLOS and JavaScript]</p><p><span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span> <span class="h-card" translate="no"><a href="https://universeodon.com/@sigue" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sigue</span></a></span></p><p>&gt; parenscript obviously doesn't have its own CLOS implementation</p><p>And achieving that doesn't seem like a five-minute job...</p><p>I am not the judge of whether that work can be justified, no matter how attractive it is.</p><p><a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a><br><a href="https://ieji.de/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a><br><a href="https://ieji.de/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JavaScript</span></a><br><a href="https://ieji.de/tags/Parenscript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Parenscript</span></a></p>
Vassil Nikolov<p><span class="h-card" translate="no"><a href="https://gamerplus.org/@screwlisp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>screwlisp</span></a></span></p><p>&gt; had to rewrite my hurkle game without using CLOS. I thought a bit about using the 'make-load-form generic</p><p>Embarrassingly, my memory fails now about what exactly happened to standardizing anonymous generic functions.</p><p><a href="https://ieji.de/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a><br><a href="https://ieji.de/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a></p>
jnpn<p><a href="https://coalton-lang.github.io/20220906-quantum-compiler/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">coalton-lang.github.io/2022090</span><span class="invisible">6-quantum-compiler/</span></a></p><p><a href="https://mastodon.social/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a> <a href="https://mastodon.social/tags/quantum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>quantum</span></a></p>
lispm<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@amoroso" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>amoroso</span></a></span> <a href="https://mastodon.social/tags/clos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clos</span></a> <a href="https://mastodon.social/tags/commonlisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>commonlisp</span></a> <a href="https://mastodon.social/tags/oop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>oop</span></a> <a href="https://mastodon.social/tags/lisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lisp</span></a> there was still a choice between various proposals then...</p><p>But the actual CLOS was not far away - the standard proposal was published in September 1988: <a href="https://dl.acm.org/toc/sigplan/1988/23/SI" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dl.acm.org/toc/sigplan/1988/23</span><span class="invisible">/SI</span></a> <br>Available above as a PDF. The final version was then published with the ANSI CL standard.</p>
Europe Says<p><a href="https://www.europesays.com/1902189/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">europesays.com/1902189/</span><span class="invisible"></span></a> Bridgepoint prices its first new issue European CLO of 2025 <a href="https://pubeurope.com/tags/Bridgepoint" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bridgepoint</span></a> <a href="https://pubeurope.com/tags/CLOs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOs</span></a> <a href="https://pubeurope.com/tags/europe" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>europe</span></a> <a href="https://pubeurope.com/tags/JohnMurphy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JohnMurphy</span></a></p>
Hacker News<p>Depending in Common Lisp – Using the CLOS dependent maintenance protocol (2022) — <a href="https://stevelosh.com/blog/2022/08/depending-in-common-lisp/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">stevelosh.com/blog/2022/08/dep</span><span class="invisible">ending-in-common-lisp/</span></a><br><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HackerNews</span></a> <a href="https://mastodon.social/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a> <a href="https://mastodon.social/tags/CLOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLOS</span></a> <a href="https://mastodon.social/tags/DependencyManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DependencyManagement</span></a> <a href="https://mastodon.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a> <a href="https://mastodon.social/tags/ProgrammingLanguages" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProgrammingLanguages</span></a> <a href="https://mastodon.social/tags/TechBlog" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechBlog</span></a></p>
Paolo Amoroso<p>A short and easy to understand finite state machine implementation in CLOS.</p><p><a href="https://www.adamjrichardson.com/posts/simple_fsm.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">adamjrichardson.com/posts/simp</span><span class="invisible">le_fsm.html</span></a></p><p><a href="https://fosstodon.org/tags/clos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clos</span></a> <a href="https://fosstodon.org/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a> <a href="https://fosstodon.org/tags/lisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lisp</span></a></p>
Paolo Amoroso<p>A 1993 case study of using CLOS for developing a blackborad system for radar tracking. The design is interesting, but that way of formatting Lisp code with solitary parentheses on a line by themselves drives me crazy.</p><p><a href="https://onlinelibrary.wiley.com/doi/pdf/10.1002/int.4550080503" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">onlinelibrary.wiley.com/doi/pd</span><span class="invisible">f/10.1002/int.4550080503</span></a></p><p><a href="https://fosstodon.org/tags/clos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clos</span></a> <a href="https://fosstodon.org/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a> <a href="https://fosstodon.org/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ai</span></a></p>
Paolo Amoroso<p>I'm looking to study CLOS code that is well designed, well documented, _and_ makes idiomatic use of mixin classes. Any recommendations other than the usual Common Lisp and CLOS books?</p><p><a href="https://fosstodon.org/tags/clos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clos</span></a> <a href="https://fosstodon.org/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a> <a href="https://fosstodon.org/tags/lisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lisp</span></a></p>
Paolo Amoroso<p>A rare copy for sale of "Lisp Style and Design" by Molly Miller and Eric Benson (Digital Press, 1990), a great book cited by Paul Graham in On Lisp that covers often overlooked topics. All the proceeds will be donated to the Medley Interlisp Project.</p><p><a href="https://www.ebay.com/itm/296823376425" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">ebay.com/itm/296823376425</span><span class="invisible"></span></a></p><p><a href="https://fosstodon.org/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommonLisp</span></a> <a href="https://fosstodon.org/tags/lisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lisp</span></a> <a href="https://fosstodon.org/tags/clos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clos</span></a> <a href="https://fosstodon.org/tags/interlisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>interlisp</span></a></p>
vintage screwlisp account<p><a href="https://mastodon.sdf.org/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a> <a href="https://mastodon.sdf.org/tags/techDiscussion" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>techDiscussion</span></a> of <a href="https://mastodon.sdf.org/tags/commonLisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>commonLisp</span></a> on <a href="https://mastodon.sdf.org/tags/itch_io" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>itch_io</span></a> .<br><a href="https://lispy-gopher-show.itch.io/moonclimb/devlog/791188/what-we-get-out-of-lisp" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">lispy-gopher-show.itch.io/moon</span><span class="invisible">climb/devlog/791188/what-we-get-out-of-lisp</span></a></p><p>: A short pamphlet about what I think you get out of lisp. Namely <a href="https://mastodon.sdf.org/tags/loop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>loop</span></a> <a href="https://mastodon.sdf.org/tags/format" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>format</span></a> <a href="https://mastodon.sdf.org/tags/clim" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clim</span></a> <a href="https://mastodon.sdf.org/tags/clos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clos</span></a> <a href="https://mastodon.sdf.org/tags/conditions" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>conditions</span></a> ie <a href="https://mastodon.sdf.org/tags/iteration" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iteration</span></a> <a href="https://mastodon.sdf.org/tags/prettyPrinting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>prettyPrinting</span></a> <a href="https://mastodon.sdf.org/tags/GUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GUI</span></a> <a href="https://mastodon.sdf.org/tags/oop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>oop</span></a> <a href="https://mastodon.sdf.org/tags/notCrashing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>notCrashing</span></a></p><p>When I remember how to get any of my tildes back I will gopher the org doc.</p>