I'm pretty sure you need a typedef to hold the disclaimer container. In fact, a typedef to hold the typedef would make it more readable. Using an autopointer would be discouraged - they aren't magic fairy dust, you know.
Make sure it is const & too, otherwise it will copy on assign. Of course, it won't actually TELL you that it did a copy, until you try to do something to the copy and discover that your value isn't what you expect in some module on the other side of your codepool.
In that case, make it const and reference counted and mutable... A mutable disclaimer does break other rules, however. For that, you'll need copy-on-write (cow). A mutable reference counted std::disclaimer will make anyone have a cow.
On the other hand, if it actually does complain about your non-const non-mutable non-reference-counted std::disclaimer, you will have absolutely no idea what the complaint is, because the error message will be absolutely incomprehendable, even when printed and delivered by forklift.
Then, there is "Please wait: linking 40mb binary" (you don't rely on the stl being stl, do you??)
<obligatory 3d web page comment> gimme a 3d screen, I'll use a 3d browser. For now I'd be happy for a wraparound taskbar.<ob>
I'm sure you have an invalid iterator there somewhere.
If you think you can't get away with a regular usb stick (i.e. if some admin somewhere grew a neuron), just leave a CD - one of them small ones if necessary, with "18th party stripper pics" written on it.../e logs out, googles for group policy autorun disable
Hand-optimization is an extremely important step in a number of fields - without the hand-optimizations of graphics engines in the "olden days", we probably wouldn't have taken quite the route we did. Making vga buffer registers work to push out a wider write than the processor was capable, etc...
An operation taking 1mS to perform sounds like it isn't worth looking at, unless you're doing it 10,000,000 times... take a few % (= a few dozen cycles) off the execution time of that can save time and $, or get the frame rate of a game back into the sweet spot, etc...
The converse, "get a faster processor" often isn't feasable - and the salary for a decent programmer for a couple of weeks doesn't ring any bells on the balance sheet if you're cranking out a million processors.
Question is, can the sharks with lasers survive in the low gravity on the moon with oxygen tanks supplied by big mirrors and lenses? Perhaps the sharks could point their lasers at the SiO2 and make their own oxygen?
Wow! Think of the possibilities!
Slashdot Mirror
>sig = new std::disclaimer();
I'm pretty sure you need a typedef to hold the disclaimer container. In fact, a typedef to hold the typedef would make it more readable. Using an autopointer would be discouraged - they aren't magic fairy dust, you know.
Make sure it is const & too, otherwise it will copy on assign. Of course, it won't actually TELL you that it did a copy, until you try to do something to the copy and discover that your value isn't what you expect in some module on the other side of your codepool.
In that case, make it const and reference counted and mutable... A mutable disclaimer does break other rules, however. For that, you'll need copy-on-write (cow). A mutable reference counted std::disclaimer will make anyone have a cow.
On the other hand, if it actually does complain about your non-const non-mutable non-reference-counted std::disclaimer, you will have absolutely no idea what the complaint is, because the error message will be absolutely incomprehendable, even when printed and delivered by forklift.
Then, there is "Please wait: linking 40mb binary" (you don't rely on the stl being stl, do you??)
<obligatory 3d web page comment> gimme a 3d screen, I'll use a 3d browser. For now I'd be happy for a wraparound taskbar.<ob>
I'm sure you have an invalid iterator there somewhere.
Lasers, and crank up the power to the "blow up tanks at 3000m" http://www.popularmechanics.com/science/defense/12 81536.html setting.
But, you don't do this as a user in the enterprise admins group, do you?
:)
/dev/nullb ofh1.html
No, of course not... more likely domain administrator itself, right?
<mumbles> dot dot dot
All you need to know: http://www.leo.org/information/freizeit/fun/bofh/
If you think you can't get away with a regular usb stick (i.e. if some admin somewhere grew a neuron), just leave a CD - one of them small ones if necessary, with "18th party stripper pics" written on it... /e logs out, googles for group policy autorun disable
Hand-optimization is an extremely important step in a number of fields - without the hand-optimizations of graphics engines in the "olden days", we probably wouldn't have taken quite the route we did. Making vga buffer registers work to push out a wider write than the processor was capable, etc... An operation taking 1mS to perform sounds like it isn't worth looking at, unless you're doing it 10,000,000 times... take a few % (= a few dozen cycles) off the execution time of that can save time and $, or get the frame rate of a game back into the sweet spot, etc... The converse, "get a faster processor" often isn't feasable - and the salary for a decent programmer for a couple of weeks doesn't ring any bells on the balance sheet if you're cranking out a million processors.
Question is, can the sharks with lasers survive in the low gravity on the moon with oxygen tanks supplied by big mirrors and lenses? Perhaps the sharks could point their lasers at the SiO2 and make their own oxygen? Wow! Think of the possibilities!
Foil hat with rabbit ears - not to be confused with a mickey-mouse hat...