Because the EU doesn't believe for an instant that the plan proposed by the Greeks will work. To be fair, I think they're right about that. However, the EU's plan is even less likely to work and will probably do a lot more damage - the IMF have themselves admitted that in recent days.
On a Vax you could dereference a NULL pointer and get zero.
Frankly I don't give a shit about your videos. I watched one once and it was amateurish and painful.
The transcript, that's what I want, and now you've provided it. Make the video as long or as short as you want, just keep the transcript.
These are not patient-portable devices. They attach to an IV pole and control delivery of whatever drug is fed from the bag. They're modular, so they get mixed and matched from pole to pole (and presumably some stash on the ward) as necessary. They are not isolated; they communicate with other systems on the ward so that, for example, the nurse can come by and check on the patient when the bag is empty.
Getting access to one of these wouldn't necessarily be that hard. Go to the ER with something that will get them to give you IV fluid and you'll find yourself left alone with one of these pumps. Install a worm and over time you'll have a lot of devices at your command and perhaps have gathered a lot of information into the bargain.
C++ templates are also Turing-complete at compile time.
When I tried learning a bit of LISP, the thing that struck me was that its metaprogramming language is also the runtime language, and I like that very much.
I'm not a Linux programmer so I may be out of date on this, but there isn't or wasn't a single C++ ABI on Linux between the various compilers. If the kernel used C++ for those interfaces it would potentially require that the kernal and all kernel modules were compiled with the same toolchain. Rolling their own implementation means the ABI is compatible across all the different compilers and compiler version with a side benefit of being able to write kernel modules in languages other than C/C++.
I read the paper and their premise seems to be that MINSETs can be browsable/searchable and good enough to let programmers figure out whether a given function is worth investigating further. Basically they're a better replacement for text search and class browsing.
I'm skeptical about that, especially looking at their examples, but I can't dismiss it outright. I think it might interact in a favourable way with metaprogramming techniques, whether C++ templates or Lisp macros, but that's just speculation.
Can you explain in more detail? It wasn't clear to me how this problem was handled. I did a little research and learned that the fast neutrons cause neutron activation, creating often long-lived radioactive isotopes of what they hit - which will generally be the reactor containment walls.
He did mention breeding tritium via lithium, so is the idea to plate the inner walls of the reactor with lithium? In that case, does the amount of tritium generated balance with the amount consumed? Or, does that just naturally reach equilibrium?
In any case, I think all of this is only alluded to in the video. If you have more insight, I think it would be useful to share it.
Build them a small form factor PC. Don't connect the USB ports and don't provide an optical drive. Install FreeDOS, a basic dialup TCP/IP stack, an email client and a web browser. I'd also set it up to decompress and restore everything from a read-only partition every single time they boot, ideally before processing config files. If there isn't already a way to do this, FreeDOS does have source available, so you could modify that.
They cover that in the full memo:
Q: Why do some supplier employees not take breaks when others do?
A: There are some business functions and processes that have been fully outsourced (Outsourcing), such as cafeteria services, landscaping and call centers. These Outsourcing engagements are limited, require a certain set of criteria be met and must go through a rigorous approval process.
Between 2 and 3 years but it did not fail, so I don't know how long it would've lasted. I replaced it with a higher wattage "daylight" bulb a few months ago. I really like the much-less-yellow look of the daylight bulbs now and I don't think I'd use any other hue.
Well it's the keys, specifically the modifier keys, that are supposed to be sticky. That doesn't imply that their stickiness can only be affected by other keys.
I just tested and OS X treats the clicks and key presses the same way when sticky keys is enabled. Hit the modifier, the next click or key press is modified. Hit the modifier twice and all clicks and key presses and modified until you hit the modifier again to unlock.
Seems very much the logical way to do it.
The spec in question - http://www.x.org/docs/XKB/XKBp... as Peter references in the bug comments - discusses StickyKeys (4.4 on page 9) and strongly implies modifiers only unlatch on key presses; mouse buttons are not mentioned. His change made the code match this reading of the spec. I have a hard time believing that's what the spec writers intended, but if so then KDE's lock checkbox really isn't supposed to do anything.
This was my reaction as well. I looked at the trademark registration, which has a picture of the Fluke, then at Sparkfun's site. So, fair enough. However, I google image searched 'multimeter' and there are lots of multimeters in that same shade of yellow, of all sorts of brands. I had no idea yellow "meant" Fluke, personally. I think there's a valid case that this trademark has become diluted and generic. Whether all those others are licensed uses or not, if there's no scope for customer confusion of brand, it's no longer a valid trademark.