News for hackers. Stuff that matters.

Akira1364

Re:Qwen3.6-Max-Preview: Smarter, Sharper, Still Evolving on Monday April 20, 2026 @01:47PM (#47837969)
IDK about GLM but GPT 5.4 Extra High has been great when I've used it in the VS Code Copilot extension, I see no actual reason Opus should consume 3x more quota than it the way it does
Re:A Guided Introduction to the Free Pascal Language on Thursday December 29, 2022 @05:27PM (#34178924)
Which Github page do you mean? I wasn't aware they'd started putting properly packaged binary releases on Github.
Re:A Guided Introduction to the Free Pascal Language on Wednesday December 28, 2022 @04:08PM (#34165984)
Don't download the bundled Free Pascal and Lazarus distributions from this site, they're very outdated. Just get the normal releases from the actual Free Pascal and Lazarus sites which are linked at the top of the page. Lazarus comes with Free Pascal bundled by default anyways, so you don't need to grab the compiler separately if using Lazarus.
Re:Zig 0.9.0 on Tuesday December 21, 2021 @12:34PM (#29639775)
I think you somewhat misunderstood the manner I was suggesting you'd be approaching things there, though nothing you've said is incorrect.
Re:Zig 0.9.0 on Tuesday December 21, 2021 @03:36AM (#29635283)
That's not really true at all. The single byte / single character comma separators are all that matters there. As long as you directly acknowledge / exactly replicate whatever blob of data happens to be in between each set of commas (even if it is nonsense garbage text) then you're correctly parsing the CSV.
Re:Patten Matching in Nim on Thursday March 11, 2021 @12:49PM (#26426828)
What exactly is wrong with Nim's docs, in your opinion? They seem fine after perusing the ones at the following link a bit just now:

https://nim-lang.org/documentation.html

Re:Time safety is more important than memory safety on Saturday February 15, 2020 @08:13PM (#22339194)
Two things:

A) The person you're replying to is simply quite wrong about the amount of Pascal libraries available. There is no "domain of interest" I can think of that does not have at least one "defacto" library for it.

More commonly though there's four, five, six or more libraries for any given thing to choose from, which often turn out to each have specific strengths such that you may very well end up using more than one of them in your project.

B) They would almost certainly probably not like Go. Object Pascal as implemented by Free Pascal is a language that effectively embraces with open arms almost all of the things that Go actively avoids: for example, traditional (single) inheritance, operator overloading, both function overloading and generics, and so on and so forth.

As far as inheritance specifically, the general indifferent attitudes towards it of "there are definitely times and places where it makes more sense than anything else to use" amongst Pascal programmers are in my opinion basically a direct result of the fact that "bad experiences the compiler developers personally had with inheritance as specifically implemented by C++" are NOT something that actively factors into their decision making process or something that they really think about or care about at all (or more broadly, something that users of the compiler generally think about or care about at all).

This sets it quite far apart from other languages such as Rust, where "things C and C++ arguably did wrong" are in fact heavily influential and both thought about and discussed regularly.

Re:Time safety is more important than memory safety on Saturday February 15, 2020 @06:18PM (#22338730)
This is a very strange comment IMO. There are already perhaps too many XML and JSON handling libraries for Object Pascal, as well as libraries for pretty much anything else I can think of.
You could write something along the lines of `writeln` using `array of const` with today's Free Pascal. It's still strictly better that it's actually implemented as a built-in for various reasons, though.

Also, yes, Free Pascal is entirely self-hosted from the bottom up, making use of inline assembly blocks in some places where it's necessary. It is to Pascal what GCC is to C and C++, basically (which is to say, it has no real dependencies on toolchains other than itself).

You use "array of const" to write the equivalent of a regular C variadic function in modern Pascal implementations such as Delphi and Free Pascal:

https://www.freepascal.org/docs-html/ref/refsu69.html

That said, as far as at least Free Pascal goes, there isn't actually even a specific function called `writeln` with a real body that you can go and look at somewhere.

It's a magic language-level intrinsic that gets broken down into calls to various other intrinsics by the compiler based on what's passed to it.

Re:Chris Lattner on the Realm WWDC 2017 Swift Panel on Sunday July 02, 2017 @12:16AM (#14680862)
TFW you code in Object Pascal and don't have C-trubz
Re:Electron is flash for the desktop (2016) on Tuesday April 11, 2017 @11:42PM (#14094576)
I tried Hyper, listed in their "apps made with Electron" gallery thing. lol 250 megabyte fancy command-prompt