200 karma · joined March 10, 2009
According to Wikipedia, this is called "sub-addressing".
def f(n):
num = 0
while num < n:
yield num
num += 1
function f(n) {
var num = 0;
return function () {
if (num < n) {
return num++;
}
}
}That's the point of this topic, to discuss things that have been done but didn't seem obvious 5-10 years ago.
These are all escape continuations.
>which unfortunately I don't have a snappy word on hand for
Abstractions?
I live in the UK and I don't know anyone with fuses in the actual outlet. We normally have a circuit breaker and fuse in the plug. For things like my PC, I also use 4-way extension cords which have an additional fuse and surge protector.
It's impossible to get it right though because you need to decide what the user wants to see localised vs always in their home locale. Maybe another header that you could set per site like "Accept-Content-Locale" or something.
And of course, both the Accept-Language and GeoIP methods fail miserably at determining things like the user's time zone. There really should be a "home" and "roaming" locale system in browsers that sends the preferred language, time zone, localised content preference, and anything else that could be useful in generically customising content. The user could set the locale browser wide or per site.
The current system forces people to make choices at a point in their lives when they don't even know who they are yet, let alone what they want to do with their lives. Instead of Google's 20% time, we need 20% education time.
Why put them in hardware? That sounds like an awful lot of extra silicon for every single architecture. Wouldn't it be better to have a higher level software abstraction like Parrot that you just build everything else on top of?
Are you actually going to have a business model then? :)
Such as? Ok, so you get better multithreaded behaviour but now you're copying state all the time and having to thread it though all your functions. Sometimes just updating state is the right thing to do.
Personally, I think a good tradeoff is immutable data but mutable references.
Say you have a function that is basically a loop processing a list of files, it throws some kind of "file not found" error. You could sort the file out and do a resume "try again", select a different file and do resume "diff file (filename)" or do resume "skip".
>Mono implements an international standard albeit one from a convicted monopolist. If this is a problem, why do people use C, the standard from convicted monopolist AT&T? Mono implements an improved, Free replacement for a proprietary offering. If this is a problem, why do people use GNU (which provided an improved, Free replacement for proprietary UNIX)?
The only way to make it work reliably is to look at the window.documentMode property which requires changing your code, thus defeating the point of the compatibility mode in the first place.
It's all implementation details. I've worked with databases where a NOT EXISTS would run a query for every source row where as an outer join would run through once doing the join and was therefore faster.