I thought the whole idea was that it was supposed to be a riff off of the name "C++."
Yes. But the name "C++" is a riff off of incrementing variables in C, which can actually be done two ways - eg: x++ or ++x. Putting the '++' after the variable means the variable is "looked at" before it's incremented. So, if Buffistas_Building_a_Better_Board = 1, and you have the expression y = Buffistas_Building_a_Better_Board++, y will = 1, as Buffistas_Building_a_Better_Board is not incremented to 2 until after y is assigned. OTOH, the expression y = ++Buffistas_Building_a_Better_Board will result in y=2 (as well as Buffistas_Building_a_Better_Board=2).
OK, that was
way
too much explanation, right?
OK, that was way too much explanation, right?
Yep, and it also perfectly matches the explanation I was given of why it really ought to be ++C
There should be more math. This could be mathier.
Yep, and it also perfectly matches the explanation I was given of why it really ought to be ++C
OTOH, if the variable only needs to be incremented, not "looked at," then the convention seems to be putting the ++ after the variable - eg, for-next loops are usually done like this:
for(x = 1; x < 10; x++){
blah blah;
}
eta: Don't ask me what "blah blah" does, or I shall be forced to make something up....
Unrelated to syntax, I have to say I hate the changes that mean a marked post is the first one displayed on the page. I liked being able to mark or unmark a post without changing what I'd "read" and what I hadn't "read." Same with blocking, etc.
Did we consider "Buffistas Building a Better Board += 1"? Actually, "Buffistas Building a Better Board << 1" would have been the nerdiest.
Edited because it's hard to type <.
Unrelated to syntax, I have to say I hate the changes that mean a marked post is the first one displayed on the page. I liked being able to mark or unmark a post without changing what I'd "read" and what I hadn't "read." Same with blocking, etc.
I would agree, except I hated much more what happened the old way. All my scrolling was undone, and I'd have to scroll back through what I'd already read, to find out where I was. If it could be leave me at the same point on the page, like a refresh does, I would like the old way better.
If it could be leave me at the same point on the page, like a refresh does, I would like the old way better.
That's between you and your browser, mostly. I mean, we could put something in that puts the post you just marked at the top of your
window
(not page), but if you had marked it while it was at the bottom of your window, you're still shifted around.
I mean, we could put something in that puts the post you just marked at the top of your window (not page)
Sorry, that is what I meant. But that isn't how it used to work, at least not for me. Before it was the way it is now, it would bring me back to the top of the page I had loaded, even if the post I marked wasn't anywhere near there. So if I was in natter, and loaded the page starting with post #51 to post #100, and then I read down to and marked post 72, it would bounce me back up to post 51. I hated that. Just sayin'.
