Groups | Search | Server Info | Login | Register
Groups > gnu.emacs.help > #60994
| From | Richard Smith <null@void.com> |
|---|---|
| Newsgroups | gnu.emacs.help |
| Subject | Re: TCO with named-let via macros |
| Date | 2024-08-10 22:28 +0100 |
| Organization | BWH Usenet Archive (https://usenet.blueworldhosting.com) |
| Message-ID | <m1ed6wawzx.fsf@void.com> (permalink) |
| References | <m11q42e6zz.fsf@void.com> <8734oi5ksx.fsf@axel-reichert.de> <m1y169hl35.fsf@void.com> <87ikw8jgnj.fsf@gmail.com> |
steve g <sgonedes1977@gmail.com> writes: > Richard Smith <null@void.com> writes: > >> Thanks Axel >> Regarding the second approach; >> I have read >> * Paul Graham's "On Lisp" >> * Siebel's "Practical Common Lisp" >> so have seen things like "gensym" and why has to be so. >> >> Reality is, with very not-advanced lisp basics I seem to do well. > > yeah me too :) > >> >> In my world of melting and shaping metal, there seems to be something >> good about the working environment of equations and explanations in one >> document. It seems to facilitate a person developing their thoughts. > > I so agree! I thread and weld pipe for fire suppression systems. we use > hydraulic calculations; if you can do this you are golden... > >> >> This seems to be the biggest issue - what the environment makes readily >> and enjoyably achievable. >> >> In recent years >> >> * every beam calculation I want to do >> (Euler-Bernoulli beam - derived 1750's; applied eg. Eiffel 1880's-ish) >> which I do use frequently in my welding and engineering work >> > > >> * a 1-D computer-numerical solution for heat-flow which proves a useful >> "nutcracker" for considering what's going on where the issue is >> conductive heat transfer > > > Oh yeah! another heat transfer variable :) >> >> * in mineral processing (considering processing metal ores - tin, >> copper, etc) I can run through calculations actually feeling very >> happy >> >> Mineral processing was last new application, a couple of months ago. >> I'm surrounded by abandoned mines here - some of the iconic images of >> Cornwall. With for me the crucial thing being that tin-mining is >> restarting here. There's also lithium here - efforts to work that. >> None of these metals "self-extract" from the "run-of-mine" ore. >> Hence mineral processing as an expertise. >> >> Thing is, those happily-done calculations enabled me to see the >> twists-and-turns the author, with decades of experience of mineral >> processing, could throw at you to get you to think through the issue. >> Layers deeper than the text alone could take you. > > > >> I had to visualise the minerals and mineral streams, then draw sketches >> which were my "model", > > > my boss still uses graphing paper and HGC3 (hydrolic calculator v3). > >> then derive the maths (concurred with the >> author's equations) - then write the elisp functions and get the >> answers. > >> No immediate jobs so having to get back to welding - but could return to >> remind of the logical path which worked for me, in those files, whenever. >> >> These were all "trivial" algebraic expressions, in computing terms. >> >> I appreciate you showing me >> where I could take my computing >> if that juncture came. >> >> Regards, >> Rich Smith > > > > Thank you! Hi there! I can hardly believe it that there is someone else out there who does metal-bashing and uses emacs as a working environment. "I so agree! I thread and weld pipe for fire suppression systems. we use hydraulic calculations; if you can do this you are golden..." I have a website weldsmith.co.uk Lots of technical things. If you want to get in contact there is a contact form. Since I wrote that post I have been volunteering at a mine museum making a replica of the "cage" of the haulage shaft - which for me is getting my hand back in in welding. Regards
Back to gnu.emacs.help | Previous | Next — Previous in thread | Next in thread | Find similar
thanks - calculate pi fn. in elisp Richard Smith <null@void.com> - 2024-07-09 19:48 +0100
TCO with named-let via macros (was: thanks - calculate pi fn. in elisp) Axel Reichert <mail@axel-reichert.de> - 2024-07-09 23:15 +0200
Re: TCO with named-let via macros Richard Smith <null@void.com> - 2024-07-10 06:28 +0100
Re: TCO with named-let via macros steve g <sgonedes1977@gmail.com> - 2024-08-10 15:56 -0400
Re: TCO with named-let via macros Richard Smith <null@void.com> - 2024-08-10 22:28 +0100
Re: TCO with named-let via macros Richard Smith <null@void.com> - 2024-07-10 06:36 +0100
Re: TCO with named-let via macros steve g <sgonedes1977@gmail.com> - 2024-08-10 16:22 -0400
Re: TCO with named-let via macros Axel Reichert <mail@axel-reichert.de> - 2024-08-10 23:15 +0200
Re: TCO with named-let via macros steve g <sgonedes1977@gmail.com> - 2024-08-11 14:56 -0400
Re: TCO with named-let via macros Richard Smith <null@void.com> - 2025-04-08 10:26 +0100
Re: TCO with named-let via macros Richard Smith <null@void.com> - 2024-07-10 06:59 +0100
Re: TCO with named-let via macros Richard Smith <null@void.com> - 2024-07-10 09:18 +0100
Re: TCO with named-let via macros steve g <sgonedes1977@gmail.com> - 2024-08-10 16:26 -0400
Re: TCO with named-let via macros Richard Smith <null@void.com> - 2024-08-10 22:51 +0100
csiph-web