5,638 karma · joined April 24, 2009
I suspect a lot of these hacks are used by an optimising compiler.
Exposing the firmware in this fashion would be a bad idea for all of these reasons. It is a good thing that SD card manufacturers don't do this any more, if they ever did.
It maybe stopped working once the OS decided the bytes were available for use (which it would only have done without the file marking that space as unavailable) and overwrote that section. I suspect defragmenting or otherwise moving the file about for whatever reason would have had the same effect.
We'd have two prime meridians. One for time and another for longitude. (Not a deal breaker but we'd have to plan for it.)
Using magic, I've renamed any files you have to remove control characters in the name and made it impossible to make any new ones. (You can thank me later.)
What can't you do now?
"Here's an optimization for when the X display is the same machine as the process."
"We've built Wayland. We all run applications on the same machine as the display and X gets in the way."
"We'd like to run applications from machines over the internet."
"We've built Wprs. It allows you to run graphical applications over a network."
That's the circle of life.....
A. A day is divided into a fixed number of smaller units.
B. Each smaller time unit is of a fixed physical duration.
C. The day cycle corresponds to the cycle of the solar day on Earth.
TAI picks A and B, allowing the solar cycle to drift from the time.UTC picks B and C, adding leap seconds to keep track with Earth's solar day cycle.
UT1 picks A and C, redefining the "second" to the changing rate of earth's solar day cycle.
It was a little quirky in that it was a two-pass assembler only if you put it inside a FOR loop and turned off unknown-identifier errors on the first pass. I was told you could write rudimentary assembler macros with judicious use of PROC but I could never get it working.
Github rejected my commit as I had the wrong email address. I then had to try and work out how I delete a commit but keep all my changes so I could commit it all again but with the correct email address.
I'm not sure exactly what I did but in my ham-fisted experimentation I deleted the commit and restored my local copy back to the way it was before my commit, losing all my work that day.
"Couldn't we rework that command to not use + separators?"
"No, far better to take that character out of consideration."
Unix: "Filenames can use control characters. I don't care if that makes pipes between commands really complicated! Add an option for NUL-separated filenames if you have to."
I hadn't considered that angle, that someone might not want to reveal their player logic to me. What you suggested was my "plan B" where instead of communicating over stdin/stdout, the players connect to m server over TCP/TLS and communicate over that channel instead.
I didn't want to do it this way because I liked the idea of running in a closed autonomous system. That ZIP file has to contain all the state of the player. Your robot is out there in the world alone and separated from their owner. It isn't just communication with a human I wanted to restrict, but any external system. Databases, helper systems, anything like that.
The idea of doing this way stemmed from playing CRobots in my teens in the late 80s. The robot has to be completely autonomous without the ability for a human to step in. I found programming a fighting robot rather frustrating in the end but I recalled the experience when I stumbled upon poker bots.
Your post may just cause me to pick up that plan B and leave trying to find that sandbox mode for Python. I'll be sure to thank you if I ever build something bigger than some rough plans in a text file.