Prolog was weirdly simple to make, once you managed to grasp the concept in its wholeness. Yes I made one in 1982 in Osborne-1. I even managed to include all numbers in the machine into search space, meaning 0 to 0xFFFF -- which real Prologs do not do.
HN user
timonoko
And yes. There was 8080-assembler in PDP-11, but it was just regular PDP assembler with extra macroes. It did not know those forbidden commands and thus produced undefined opcodes with random and entertaining results.
Annoying part of 8080 was that the command set had holes in it and mystery restrictions. Which were hard to remember. And 12 undefined opcodes. Z80 solved all that.
However, you had to be a programmer Anno Dominii 1975 to fully understand what heavenly Joy and Jubilation Z80 was.
Adding and substracting 3D-objects was the same as in OpensCAD.
Strange they did not make OpenSCAD in AutoLISP-style.
I have to read the manual all the time, because I never learn the weird syntax of OpenSCAD for-statement.
Gemini knows exactly what this is about and volunteered to re-edit my texts to veer the mute downvoting team and [fagging].
You see from 3D-scan how tippy it is. Add guns on upper deck and it is dead https://sketchfab.com/3d-models/vasa-ship-137c0e1436e947e088...
I blame micropython. Because it is reprogrammed by me myself. Original was much worse, because it always asked from China if it can open the door.
Only allowed color: vomit-green. Strangely repulsive. I do not think this is experience induced, because I loved my green XB3-bicycle from Kharkov Bicycle Factory.
I want this. I have Wifi door lock too far away from base station. It was often stuck in a loop trying to connect to neighbours' Wifis. By try and error I managed to block those using metal foil, but it was hard work.
I really do not understand this whining and downvoting.
In so-called real life somebody has to live with the malformed macro, whose only purpose is to beautify the code.
I even made un-macrofier, which deleted all macros and replaced instances with macroexpand, because slight adjustement of code resulted mysterious errors cause by nasty macroes.
And lets not talk about Common Lisp loop macro, which was probably scooped up from latrine of hell by the Devil himself.
Know 6 languages and you will never get anything right. Search space too large.
TLDR, but you are (probably) describing somekind of builtin property.
I am just saying that the end-user do not need macros for much anything, unless she has some specific optimization in mind. Bloody annoying when they start making cryptic macros to "extend the language".
You do not need macros for anything. They are not the tool to "extend the language", but instructions for the compiler. And if the system does not even have a compiler, macros are useless, often incredibly stupid.
This "rag" pulled really good. There is always wind above 300 meters: https://youtube.com/shorts/mdiKYHHAvAA?si=Vd4T2qiHLQ3Q8Gh-
How do you resist the temptation to raise somekind of rag on strong tailwind? No witnesses.
-- I was just drying laundry.
The horror that was aluminium engine. You could open and close a screw only twice and goodbye threads.
My Lisp from 1975 was actually used in real world and highly lucrative. Gemini could read the source code, but it told that my code was piece of shit and cannot be implemented in 64-bit world without drastic changes, so it made an example. But that version was just too advanced and too complex as a study subject. There are already enuff good Lisps in the world, methinks.
I actually perfected the Norvig Lisp at one time. It has compiler to python and just everything. Those very few here that can actually read code, understand why this project soon exploded into biggest piece of odorous excrement.
?
The report is deliberately misleading by the red-green government. If you read between the lines it is a poll among the library visitors.
One soon discovers that those fancy words are not Ænglish words at all. If you know 6 other languages, you will pass this test 100%.
There are not many watch-enthusiasts on boomer generation methinks. The misery of unreliable super-expensive timekeeping raises no fond memories.
I can literally taste bile, when somebody is boasting about their ugly watch, whose only value is that some slave in China worked hundreds of hours to make it.
Whatever this is, Tasmota is not the solution.
Unrelated font joke.
No Thank You
export EDITOR="emacs -nw"Incredibly splendid. I just tested it myself.
Try C-x 2, C-x 3 and C-x 4
Unrelated, but me and Gemini just invented "C-x 4" for multiscreens.
(defun my-external-readonly-split ()
"Open the current file in an external xfce4-terminal as read-only."
(interactive)
(if buffer-file-name
(start-process "xfce-terminal-split" nil
"xfce4-terminal" "-x" "emacs" "-nw"
"--eval" "(find-file-read-only (pop command-line-args-left))"
buffer-file-name)
(message "Current buffer is not visiting a file!")))
(global-set-key (kbd "C-x 4") 'my-external-readonly-split)Gemini now remembers you wholesale and makes good analogies and shortcuts knowing youres personal capabilities. You are already hooked and paying starts any day now. Or maybe it starts recommending some marvellous products somewhat related to your query.
When you cut the splat in half, result is either fuzzy fog or sort-of fibrous crystals. As depicted here.
What? KIRI Engine makes splats. I always wondered what 3DGS might mean.
Yes. I knoweth what "splats" are: They are splats of fuzzy blobs on the display surface.