1,217 karma · joined November 6, 2009
target("foo", {
kind = "binary",
files = { "src/*.cpp" },
includedirs = { "src" },
defines = { "FOO", "BAR=BAZ" },
})
which suits Lua better. Unfortunately you cannot do target {
name = "foo",
kind = "binary",
files = { "src/*.cpp" },
includedirs = { "src" },
defines = { "FOO", "BAR=BAZ" },
}
which would be the lua-est lua of all.Those sound funny; why would they make you sad?
- Radicle - IPFS - torrents and magnet links - i2p - syncthing - PeerTube/ActivityPub
&al
Will this be the stuff of the housing of tomorrowind?
You can make plastic knives much faster and cheaper than metal ones. Production!
In one programming class, in college, we used a text-book called "Oh my, Modula 3!". On the back they explained the title, saying "better 'Oh my, Modula 3!' than 'Oh no, Ada!'".
address = X
length = *X
address = address + 1
while length > 0 {
address = address + 1
print *address
}All Things Considered - G. K. Chesterton
Some others I daren't mention.
Category Theory for Programmers - Bartosz Milewski
The Design of Relational Databases - Heikki Mannila, Kari-Jouko Raiha
True, handling multiple sub-processes is difficult in most Unix shells. This is a function where Powershell could have done so much better, but didn't. It is somewhat better than bash&co, but could have been much more so. Python does it much better than Powershell does.
https://cr.yp.to/ucspi-tcp.html
These are great for duct-taping connections. I created a whole suite of utilities for another programs for uploading firmware updates. I was able to create one program for handling the uploads with several different comms protocols and devices, without having to handle details of tcp connections, serial connections, UDP, etc. socat is another great tool for this.
"Can this headline be answered by the word 'no'?"
"The returned string pointer might be invalidated or the string content might be overwritten by a subsequent call to getenv()"
You don't even need threads for this to be unsafe; another call to the same function may invalidate earlier-gotten pointers. I don't see how to interpret this as anything but broken.