The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
just finished a binge watch of mr. mercedes season 3. Good, easy, plausible. - yeah season 2 was a bit implausible, but s3 barely brings that up, all of 2 brief mentions
but best part is it ended, no loose strings, everything closed,and no new plot teasers...
It actually ended! Refreshing. No waiting for more.
so used to there being some new twist revealed [right at the end], unfinished / branch [sub] plot, or sometimes straight-up in-your-face hints pointing to [the producers milking] a new season only to have the executives claim 'not enough audience' (reality not enough $).
otoh also fair to add a lot of the MM cast were pretty old of a more senior persuasion; nothing kills a series faster then a lead actor kicking the bucket mid stream - maybe a risk management call?
<< Signature removed due to multiple copyright violations >>
You would not say that if you knew Mr Mercedes. No doubt he will have another 1000 changes to everything I delivered him today. For the rest of the year he is out of luck. I still had a few free days left. See you in january.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
Now I'm a little scared. Because code that I knew was broken is working but when I "fixed" it the whole thing falls on its face.
The problem is, given a bit of code, find all variables declared within the scope of that code.
Prior, i was just getting all the variables in the routine. I knew it was wrong, but i hadn't worked out the problem yet.
Now I have, so I went back to update the code. As soon as I put it in Slang's patcher stops finding some of my variables!
So I test the variable tracer some more. It works as good as I could have hoped.
Which means somewhere, something else doesn't. And I barely know where to begin to look because of how this works.
Worse, currently my repro requires running a very particular bit of slang code as part of my lexer generator - "Rolex"'s operation, which means i had to pull that out and duplicate it in a scratch binary to debug, but it's still not very narrowed down. I can't quite find the bit where i need to test in the debugger.
The trouble is visitors are nasty when things go wrong. The visitor works right, it's the code that's firing on visit that's bad somewhere, and that happens inside a visit so the call stack is a nightmare.
And it's friday the 13th. Just my day. Maybe I should stay off the computer.
Building stuff like this is rough.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
Shouldn't that be 'loaded for Berra'? Though I'm not sure as I'm feeling just av er age today.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle