explanation: there's a missing comma between the first and second elements. this would normally be an error, except python automatically merges strings, even with whitespace in them.
so the contents of values right now is ['ab', 'c']
explanation: there's a missing comma between the first and second elements. this would normally be an error, except python automatically merges strings, even with whitespace in them.
so the contents of values right now is ['ab', 'c']
@jbqueru yeah but I expect C to be backwards and user-hostile, it's a portable assembler from 1972!
This is one of my least favorite python syntax features:
>>> values=[
... 'a'
... 'b',
... 'c',
... ]
>>> 'a' in values
False
I'm currently working on rewriting Where in the World is Carmen Sandiego? in FastShow.
My website is powered by MonkeyDust compiled to WASM.
Back in college I worked on an image searching system written in LittleBritain
@mjg59 I'm exceptionally proud to be a level of fuckery.
(though my wife suggests it should be a unit, raising the obvious question of what "1 foone" is)
my programming language hot take is that python-inspired languages shouldn't be named after snakes (eg cobra/boa/serp*nt).
Python is named after Monty Python. Python-inspired programming langues should be named after British sketch comedy shows, damn it!
See? over in the Control Panel, you can see there's already this select-a-color dialog.
Huh. Why does Microsoft Paintbrush use three RGB sliders rather than the standard color selector dialog?
(It definitely existed as of Windows 3.1!)
two theories:
1. this dialog is the one that WILL BE standard, but it's not standard yet. possible! I don't know when the color picker was added to the API. maybe it wasn't yet, or it wasn't when paintbrush was finalized.
2. it's because of the pre-windows/pre-microsoft history of paintbrush
FUCK I just realized I have a reason to fix this.
I was hoping to finish today without having to reverse engineer MSPaint
ZSoft PC Paintbrush Plus 1.12 for Windows (which predates windows 3.1) has the identical dialog.
it's slightly surreal to try and run a program only for Windows 3.1 to go "Watch out, this is some legacy software, and might not work well on modern 1992-era operating systems!"
I need more youtube channels where they're going over the code of reverse engineered games
just Displaced Gamers isn't enough, even if super awesome.
pass one resulted in 12313 errors. that's not TOO many!
the problem with working with any non-trivial dataset of any kind, is that you can almost always write code to process 95% of the entries in a short period. then it takes 10 times as long to handle the remaining 5% of weird outliers
that's only like 1 error per 3 lines of source
you'd think a disassembler that can export x86 assembly and an assembler that can accept x86 assembly would be trivial to combine!
and they both use intel syntax x86 assembly, not at&t!
my current Stupid Project is a pipeline to (semi-) automate extracting a ghidra project into source it can run through NASM.
but no, x86 assembly is not compatible between assemblers usually because they're all different.
I got it down to 6, fixed one of those, and now it's down to 629
apparently I've now made it to a later pass of the assembler so it's reporting more new errors
Hardware / software necromancer, collector of Weird Stuff, maker of Death Generators. (she/they🏳️⚧️)
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.