8xde0wcNwpslOw
Joined 9 years ago
Joined 9 years ago
What's more, in bad weather people (who have the option to choose between public transportation and their own vehicles) tend to choose cars more often because public transit has a habit of becoming increasingly unreliable, especially due to winter conditions, even though such conditions can be reasonably expected for 6 months a year.
The odd thing about this is how the biking paths around here (a city 60N) still remain relatively empty for a long time in the winter. It almost confuses me, but not really :-)
Enjoy the break at least.
The funny thing is, even when decompression "works" on Windows 10 (that is, when you join hands in prayer and don't disturb the machine), you could theoretically just download the decompressed files faster over the internet. I can only guess the there's something fundamentally broken about Windows and file systems because many operations are so ridiculously slow no matter the hardware. It's perhaps my biggest gripe about modern Windows, aside from the actual desktop (working with multiple windows) being very bare and annoying to use, useless set of default applications, and that the built-in localized keyboard layout is obsolete and thus quite restricted as far as punctuation goes.
From my past experiences, I must unfortunately say that you might be just about the last person they want to, or can discuss it with (as strange as that sounds), but without them confronting their habits, it is unlikely it is going to get easier. Even with crippling forms of OCD, it is easier to just "comply" than to challenge it, the latter being "guarded" by great anxiety that feels much more intimidating than even the most time-consuming and difficult routines, even if they fully realize some of the irrationality. (That, too, may be hard to understand from another person's view.)
So, should you put spaces at the end, or at the beginning of lines in text that's broken into multiple lines?
Both of course, people tend to want it all, and dreams to pay for it all. In 100 years it'll supposedly all work out fine, despite "short term" problems, no need to compromise.
I'm sorry you have to withstand the opposition from those who have to weather the problems in the meantime. Perhaps a loaner crystal ball could help us weave our reservations.
array[x] and *(array+x) are indeed equivalent for any identifiers 'array' and 'x' (assuming one of those evaluates as a pointer value, and the other as an integer value; otherwise the code is incorrect). In fact, in this context an actual array is not subject to either unary-& or sizeof operators, so it evaluates to a pointer value, fulfilling the precondition.
This is why "array subscription" also directly works with pointers (i.e. "ptr[x]"), and from the equivalence above follows one of the common useless facts that you can swap the identifiers (i.e. "x[array]").
(This comment is probably confusing enough without saying that "(&array)[x]" is valid code too, but isn't the same thing as those before.)