Hydro does this very easily. You put exactly enough water through the gates to match demand, and leave the rest to back up behind the dam for later use. Too much water? Just overflow a little, bypassing the generators.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
You do realise every single MP for National voted for the Copyright Reform Bill, right? You realise that they strongly support section 92A, right?
Have you ever tried $X - > member (where $X is an instantiated class object?)
That's not whitespace around operators. That's replacing one operator with two (minus and greater than). Of course that'll make a difference, but my point was that whitespace around the operator currently doesn't and shouldn't in the future. Don't misconstrue it. To be clear, the reason meaningless whitespace around operators is is that both of the following work the same way:
Now, though, you're proposing that namespaces shouldn't be allowed to have the same name as any variable, class or constant. Are you mad? You realise that name conflict resolution is what namespaces are for, right? Yet you want to make it the case that if I'm using a Date namespace, I can never have a variable or class called date/Date? That's crazy.
The "just make sure your names are memorable, distinctive, and you're good to go" rule is what PHP currently has, with class names for instance. And it's the problem that namespaces are designed to solve, not make worse.