Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pklausler
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
91.
▲
by
pklausler
10mo ago
Table-driven parsers with custom per-statement tokenizers are still common in surviving Fortran compilers, with the exception of flang-new in LLVM. I used a custom parser combinator library there, inspired by a prototype in Haskell's
92.
▲
by
pklausler
10mo ago
It goes back to the CDC 6600 at least, and is most often seen as part of Hamming distance computation (pop(xor(x,y))). But it turns out to be really useful for other things (trailing zero count), and worth having in hardware since the soft
93.
▲
by
pklausler
10mo ago
Universally distinct would seem more correct than unique , at least mathematically speaking, unless there's only ever going to be just one of them.
94.
▲
by
pklausler
10mo ago
It was invented so that IBM could sell more gear to the institutions that employed them.
95.
▲
by
pklausler
11mo ago
Fortran compilers were historically implemented by hardware vendors in order to sell their hardware, and this still largely holds true across the surviving implementations with the exceptions of GNU Fortran (obviously) and nagfor (commercia
96.
▲
by
pklausler
11mo ago
I really don't understand the disdain for Fortran on HN. While it's not the most well-defined or portable programming language in the world, it does its job pretty well for those who need it, and has more actively maintained impl
97.
▲
by
pklausler
11mo ago
That’s what was done on the CDC 6600 with two handy values, B0 (0) and B1 (1).
98.
▲
by
pklausler
11mo ago
What "certain versions" of Fortran since Fortran II did not have the ENTRY statement?
99.
▲
by
pklausler
11mo ago
Fortran used to have DO loops. It still does, but it used to, too. Algol's the one with FOR loops.
100.
▲
by
pklausler
11mo ago
You really think that Perl has billions of lines in active use in critical applications and libraries?
101.
▲
by
pklausler
11mo ago
LLMs are so very good at emitting plausible, authoritative-sounding, and clearly stated summaries of their training data. And if you ask them even fundamental questions about a subject of which you yourself have knowledge, they are too oft
102.
▲
by
pklausler
11mo ago
Do these tools support Nikon's "high-efficiency" compressed NEF files? I suspect that they're encumbered by patents.
103.
▲
by
pklausler
11mo ago
Even a short summary of the Wake can suffice to get you started. You're never going to understand it all, and that's okay, but even a brief chat with a Wake fan can give you the basic clues of its structure and the HCE/ALP S
104.
▲
by
pklausler
11mo ago
I don't think that English changed as much, but I could be wrong. Shakespeare's not hard for a modern English reader, given a decent edition with vocabulary hints in the footnotes. I got through most of it as a sophomore.
105.
▲
by
pklausler
11mo ago
I think that English might have fewer opportunities for this sort of thing; I found Beowulf to be surprisingly dull in the original. Greek, on the other hand, has lifetimes' worth of good stuff in its ancient forms, and can really rewa
106.
▲
by
pklausler
11mo ago
Your previous readings of Finnegans Wake are your preparation for your next one.
107.
▲
by
pklausler
11mo ago
If you think spell(1) is AI, you misunderstand at least one of them.
108.
▲
by
pklausler
11mo ago
Pedantically, will this be one mean solar light-day, or one sidereal light-day?
109.
▲
by
pklausler
11mo ago
It's a valuable but scary experiment to query an LLM on basic subject matter in a field that you know a lot about. Ask those basic questions first.
110.
▲
by
pklausler
11mo ago
LLMs, kind of like Bill Bryson's books, are great at presenting "information" that seems completely plausible, authoritative, and convincing to the reader. But when you actually do know the truth about a subject, you realize
111.
▲
by
pklausler
1y ago
This comment is 35 years out of date.
112.
▲
by
pklausler
1y ago
Fortran is recursive by default.
113.
▲
by
pklausler
1y ago
Why?
114.
▲
by
pklausler
1y ago
FORTRAN '77 conforming code is (almost) always Fortran '90 conforming code too.
115.
▲
by
pklausler
1y ago
If you want your packages delivered in order, without duplication, whenever it is not impossible to get them to you -- don't use a fulfillment company that might send you multiple boxes, or get them out of order, or not deliver them at
116.
▲
by
pklausler
1y ago
And so have the various editions of standard Fortran. In fact, ISO Fortran’s abstract floating-point model is so old now that it’s confusing, since it’s basically IEEE-754 but off by one in its exponents.
117.
▲
by
pklausler
1y ago
> We’re ultimately here to make money, not just pump out characters into text files. Different projects have other incentives. Dealing with AI slop from internet randos is a very real problem in open-source codebases. I've pretty
118.
▲
by
pklausler
1y ago
You don’t have to worry about the order of evaluation. It doesn’t seem like a big deal, until you have a big messy problem with data-dependent interdependency. Also, every list is a generator, and every indexable container is an instance
119.
▲
by
pklausler
1y ago
I wish so badly that there were a statically typed, pure, and lazy Scheme.
120.
▲
by
pklausler
1y ago
That's a reasonable assumption, but it turns out to rarely be the case with WG5/SC22/J3. There are exceptions (like SIND, SINPI, &c.), but most new features in Fortran standards are committee inventions without prototype
More ›