I have a head-torch with a pretty good compromise. The bay either accepts the proprietary battery, or three AAA batteries. The supplied lithium battery lasts longer than the AAA, but it's nice knowing the device will outlive the battery
The casino will break even, but for the gamblers there will be a small number that win big, and a much larger number that lose out.
Consider two rounds, there's a 25% chance you 4x your money, a 50% chance you 0.75x your money and a 25% chance you 0.25x your money
In the UK cell numbers start with 07 and landline numbers start with 01. And there is no region encoded in a cell number, but landline numbers begin with an area code.
Not all the landline numbers start with 01, all the big cities and urban areas got moved into 02 to make space decades ago when there was concern we might run out of space.
Also, 03 is guaranteed to cost the same as 02 but has no specific geographic link, so it's often used for helplines, customer service, that sort of thing, and for people who want to have a landline (or multiple landlines) but do not want to reveal their location.
04, 05 and 06 are part of that roped off space we reserved in expectation of a need that's now unlikely to ever materialise, oh well. In the era when it was conceived people thought "Internet shopping" was a ludicrous idea and still imagined "Video calls" would be a thing you'd do as a telephone call somewhow - so what did they know.
07 as you said is where non-geographic mobiles live, as well as some other services at similar price points
08 is "free" or sometimes revenue sharing prefixes and the 09 prefix is where "premium" services live, you know "Chat live now to singles in your area".
"anything stored in that pointer to memory you got back from malloc() is stored in an area of ram called "the heap", which is moderately slower to access than it is to access the stack."
Is this true, or a myth? Ignoring the allocation cost and access patterns making cache misses more likely, surely memory is just memory
By definition, everything on the heap got where it is dynamically, so the minimum number of pointers to chase to find it is 1.
In contrast, what’s where on the stack can often be (and often must be) known statically by the compiler and accessed directly, even moved entirely out of memory and into a register. (It’s possible to do this with suitably constrained dynamic allocations, but the optimization is much harder.)
Some architectures (e.g. the 65816, the 6502's "big brother" used in the Apple IIgs) include stack pointer relative addressing modes, which will complete the memory read and return data faster than the same instruction with a full address encoded.
Many architectures have hardware support for stacks, which could be slightly faster than arbitrary load/stores. Only works in the function owning the stack frame of course, if you pass a pointer to a stack object somewhere else, it's back to being normal memory.
I'm pretty sure this is still the case. I'm not sure how cross-platform that assumption is (it won't work in Go where it has heapstacks I don't think), but classically yeah the stack is put is slightly faster memory with fewer access barriers.
I believe that’s inaccurate, at least on a modern CPU. The bookkeeping for the stack is faster, since ‘allocating’ and ‘deallocating’ is just subtracting from and adding to a register. And the area of the stack in active use at any given time is usually tiny (well under a kilobyte, even though the full stack is usually several megabytes), so it’s likely to stick around in L1 cache. And return addresses on the stack get special treatment by the branch predictor. But other than that, it’s treated the same as any other memory.
I think you can accomplish interest rate hedging with Eurodollar (apparently now SOFR) futures contracts which are traded on open markets? But I agree with the other poster that OP should find a finance person.
Addresses in Scotland use a slash to separate flat number from street number; e.g. 15/4 West Wallaby Way is equivalent to Building 15, Flat4, West Wallaby Way.
I've had multiple websites tell me that my address isn't valid, and some delivery companies remove the number after the slash so the delivery driver knows which building, but not which flat.
To me, this is very similar to the recent post about email address validation. Very often, companies feel the need to validate certain inputs themselves and do a terrible job, when there's a better solution.
When it comes to addresses, if they're in the U.S. there is an easy way to validate delivery addresses - the USPS. They offer free access to an API that includes address validation, and thankfully most shipping services now use it. Some services still screw things up, but its less of a problem than it used to be. I notice that the Royal Mail equivalent is paid. Perhaps that's part of the problem, or perhaps the Royal Mail validator fails addresses with slashes in it.
I also noticed that the Royal Mail is a publicly traded company. I'll uh, refrain from commenting on that.
> the USPS... offer free access to an API that includes address validation, and thankfully most shipping services now use it.
Unfortunately not all. My street "number", like 100,000 other houses near me, includes a letter in the middle. USPS will happily validate it correctly, but there are still websites I encounter from time to time that complain or refuse to work.
Where I am, 100 years ago, if your house wasn't inside a city, it simply didn't have an address. The fire departments got together and created a geographic encoding scheme that would allow them to find a house if they needed to. In the 1960s, the USPS adopted it as official. New homes continue to be issued addresses according to the scheme, even though it is not rural at all - it's inside one of the largest metro areas of the US.
If you don't mind, which metro area is this? I have an interest in street grids and address numbering systems; this just sounded like a peculiarity I'd like to read up on.
Based on your recent comments, it’s right in your own backyard! Formerly and currently unincorporated DuPage and Kane counties. It seems that you have to build a new street inside an established municipality for those houses to get “normal” addresses.
FYI, I went to college in the 90s with a kid that lived in a rural area in a very low population county in Indiana (one stop light in the entire county). His house still had the old rural route addressing (your address was the box where you received mail - potentially miles away - and not a street address as commonly understood https://pe.usps.com/text/pub28/28c2_021.htm).
The addressing system in New Zealand is also some especial "I have seen things" and I never worked on it but my colleagues said that Tokyo was also "you should pull up a chair"
NZ is exceedingly plain so I don't get that comment. Most are of the form
1337 Great North Road
Pt. Chevalier
Auckland
1002
You could even omit Auckland as it's implied by the simple 1000-series postcode.
The property boom may have led to subdivisions making a 1337/2 necessary but the vast majority of buildings outside of metro areas are detached, single family properties.
My house number is 12-16. Even some government websites in Germany can't handle that and go with 12 ( which, to be fair, works for all purposes, but it's incorrect)
A lot of IDEs (I know Eclipse and VSCode both do this) will create a copy of the file you're working on each time you hit save. You can then navigate back through the local history of the file.
I'm conditioned to hit Ctrl+S with almost every change, so this gives me a very detailed history of my revisions.
It does here also in newer homes. But just getting it into the switch and then shoving everything back in the box is a challenge. Smart switches are much fatter than normal switches, and by boxes at least were wired with hard copper that was difficult to shape. I had to take out the switch for my cabinets to make everything work.
reply