Can anyone recommend some good books on Qt?
on
In-Depth With Qt 4.4
·
· Score: 1
Because I can never find any (or on GTK+) in my local bookshops.
And no , I'm not going to learn online and get eyestrain and a stinking headache staring at a monitor or spend a fortune printing out an online manual. Before anyone suggests it.
...use Java or some other high level language or even just smart pointers. Thats not what C++ is about. Besides which the language is bloated enough already.
... was one of those old moonlets paying its last visit to earth. If it had left a Langraigian point it could still have orbited very near earth for a long long time until one small nudge put it on the trajectory for that fateful day.
"What do you think regenerative braking is? You gain energy back when you brake. "
Err yes , but you don't generally regain the energy when accelerating do you. You might want to re-read what you wrote.
"better milage on a diesel when accelerating..."... than a petrol powered car. But not better mileage than when cruising in the same diesel car which is what you originally stated.
The audi that won lemans won it because it didn't have to pit so much , not because it was any faster or accelerated better.
"(Basically, electric motors deliver the most torque at close to 0 RPM)"
In theory they do , in practice if you give a motor max voltage at 0 rpm it'll just overheat and burn out. Thats why electric trains require complex motor control systems. I suspect the same is true of cars though to a lesser extent.
"Acceleration is the only place where a hybrid can make up gas milage, mostly due to regenerative braking"
Regenerative braking when accelerating? Thats a new one.
Hybrids work well in traffic. Instead of having the engine idling doing 0 mpg it can either be used to charge the battery or , if the battery is already charged just switch it off and move under electric power. "
"A diesel helps because it uses about the same amount of fuel accelerating as it does when cruising."
Who told you that?? Acceleration is putting kinetic energy into a mass (the vehicle). This requires more fuel than just cruising which is simply overcoming friction and air resistance - the kinetic energy remaining unchanged. Also anyone who has driven behind a labouring diesel vehicle can see its dumping huge quantities of fuel into the cylinders by the black soot coming out of the exhaust.
Even the most efficient diesel engine is doing 0 mpg in stationary traffic. Instead of wasting that fuel either switch the engine off and crawl on electric or use it to recharge the batteries. Hybrids are good in traffic , less so on long runs. Horses for courses.
"KDE 4.1 is out, and bugs aside, it looks promising. T"
Come out , what kind of stupid comment is that?! People slam MS for shipping buggy code but when its OSS , weelll thats ok right? Hello? Double standards anyuone? No its not ok. If its still full of bugs it should have remained as an rc , not an official release!
... he'd better start worrying because it means his friend is a resurrected zombie! Run!
Seriously , if someone is dead they're dead. Gone. No more. And don't give that "soul gone to heaven" nonsense. If their left no will then any attempt at second guessing their wishes is a waste of time and effort.
They're exactly the same thing it you're working with connection orieted stream sockets and arn't interested in settings flags or getting OOB data idiot. As for Windows , who gives a shit about that OS and its bastardised version of posix.
"How about you? Under your coding paradigm (whatever it is), do you have some magic method of proving that there are no leaks? "
No, but I wouldn't be so bloody arrogant as to state that I never have.
"is easily solved by using a vector of char to hold the packet's contents"
Err why would I ever want to do that? You think I want to add one character at a time?? And how exactly would I get the internal pointer to use in a read()? Either you've never done network coding or you're just an idiot.
"It's a matter of the compiler taking those libraries and totally fucking with their intended purpose because the language spec lets them and it can improve optimizations."
Yeah , because adding the "volatile" keyword is such a chore.
"I'm glad idiots have opinions."
Me too , and when you get an opinion that makes sense instead of talking out your arse and finding some non example that you've obviously desperately searched long and hard for on goodle, get back to me.
"I've used an embedded language nesC"
Let me guess , written by your professor for your CS101 beginners course.
Every little niche language has its fanboys, especially in the web development world (no idea why , maybe the sort of people who do web development are more excitable than other coders) and ColdFusion is no exception. So there will be lots of "noise" about it on the internet and this is what this guy is picking up with his stats.
"I have not coded a memory leak or buffer overrun in C++ in over six years."
That you know of.
"The best way to avoid overflowing raw buffers is to not use raw buffers. Use the containers. When you think you can't, think harder."
yes , nice soundbite , but in the real world things arn't always that simple. For example in network data processing you might have to read a packet header , check the size then allocate enough memory for the packet and read it in mapping a number of structure pointers onto the character buffer. Try doing that in any efficient way using the STL.
"At the moment, the C language standard is simply broken for multithreading"
Total BS. The pthreads library works and it works well and so do the equivalent libs on MS Windows. Just because you might find it hard means nothing.
"suitable language for multithreading. It's built into the language itself, like garbage collection is."
You mean it makes it easy for novices. Oh incidentaly , what language do you think the Java VM is written in? Java? Bzzzt , wrong. Its C and assembler. So how do they manage to get the threads working then? It must be magic!
Something else you might want to note is that some problems are best solved by multiprocess rather than multithread , and for that , really Java sucks badly.
".I know it can be done, but C is hard to program for a single core"
I think the translation of that is "I find C hard to program" since single core processors have been the default for most people using C for the last 20 or so years!
"Multicore support may take it over the edge."
Err why? You think programming multicore in C is hard , try it in assembler. At least with C you can always take the easy option and use threading libraries.
Most people use the STL just for dynamic arrays and maps. If you're a half decent programmer its not too hard to role your own (though admittedly a nuisance to have to do so). So no , I wouldn't say knowing the STL is a minimum requirement for programming in C++, in fact for many years before the STL came along C++ chugged along quite happily without it.
"A CD is laughably simple technology, an engineer 100 years from now will build a player (in a way that may not look anything like our current players) in no time at all"
Rubbish. For a start CD players are not simple devices otherwise Edison would have invented them. (Just because something is now a commodity item doesnt mean anyone could build one from scratch). If you;re uncomvinced go study the maths on auto focusing an pit tracking lasers, not to mention D/A conversion, reed solomon error corection etc.
Secondly , skills are lost over time. Try finding someone now who could build a decent siege engine or longbow that would be good enough to fight a medieval battle. Hell , even finding someone these days who can rebuild steam engines is tough!
So in 100 years time, building a CD player from 1st principals could well be a tough call!
At that alititude you're for all intents and purposes in a hard vacuum. There would be no oxygen for the engines and even more worrying , no air for the wings or tail to work with. Even if it could get up that high using a rocket booster it would just tumble out of control.
Slashdot Mirror
Because I can never find any (or on GTK+) in my local bookshops.
And no , I'm not going to learn online and get eyestrain and a stinking headache staring at a monitor or spend a fortune printing out an online manual. Before anyone suggests it.
...use Java or some other high level language or even just smart pointers. Thats not what C++ is about. Besides which the language is bloated enough already.
... was one of those old moonlets paying its last visit to earth. If it had left a Langraigian point it could still have orbited very near earth for a long long time until one small nudge put it on the trajectory for that fateful day.
"What do you think regenerative braking is? You gain energy back when you brake. "
... than a petrol powered car. But not better mileage than when cruising in the same diesel car which is what you originally stated.
Err yes , but you don't generally regain the energy when accelerating do you. You might want to re-read what you wrote.
"better milage on a diesel when accelerating..."
The audi that won lemans won it because it didn't have to pit so much , not because it was any faster or accelerated better.
"(Basically, electric motors deliver the most torque at close to 0 RPM)"
In theory they do , in practice if you give a motor max voltage at 0 rpm it'll just overheat and burn out. Thats why electric trains require complex motor control systems. I suspect the same is true of cars though to a lesser extent.
"Acceleration is the only place where a hybrid can make up gas milage, mostly due to regenerative braking"
Regenerative braking when accelerating? Thats a new one.
Hybrids work well in traffic. Instead of having the engine idling doing 0 mpg it can either be used to charge the battery or , if the battery is already charged just switch it off and move under electric power. "
"A diesel helps because it uses about the same amount of fuel accelerating as it does when cruising."
Who told you that?? Acceleration is putting kinetic energy into a mass (the vehicle). This requires more fuel than just cruising which is simply overcoming friction and air resistance - the kinetic energy remaining unchanged. Also anyone who has driven behind a labouring diesel vehicle can see its dumping huge quantities of fuel into the cylinders by the black soot coming out of the exhaust.
NY state: "Give us our tax!"
Amazon: "No , what you going to do about it, we're outside your juridisction!"
NY state: "errr.... please give us our tax?"
"A biodiesel hybrid makes zero sense."
/dragster guys, they obviously havent noticed yet.
No , they make perfectly good sense.
"The extra weight of the hybrid system generally doesn't make up for gains in acceleration"
Who cares? How many people who buy a hybrid give a damn whether they can beat a GTi off the lights?
"gas engines are such pigs when accelerating"
Yeah right, you better tell that to the F1/Nascar/Indy
Even the most efficient diesel engine is doing 0 mpg in stationary traffic. Instead of wasting that fuel either switch the engine off and crawl on electric or use it to recharge the batteries. Hybrids are good in traffic , less so on long runs. Horses for courses.
Ah hell , just spotted its an alpha , ignore my stupid comment.
"KDE 4.1 is out, and bugs aside, it looks promising. T"
Come out , what kind of stupid comment is that?! People slam MS for shipping buggy code but when its OSS , weelll thats ok right? Hello? Double standards anyuone? No its not ok. If its still full of bugs it should have remained as an rc , not an official release!
"incorporating semantic application elements,"
Oh great , more bloatware, just what we need when KDE isn't exactly quick to start with.
... he'd better start worrying because it means his friend is a resurrected zombie! Run!
Seriously , if someone is dead they're dead. Gone. No more. And don't give that "soul gone to heaven" nonsense. If their left no will then any attempt at second guessing their wishes is a waste of time and effort.
They're exactly the same thing it you're working with connection orieted stream sockets and arn't interested in settings flags or getting OOB data idiot. As for Windows , who gives a shit about that OS and its bastardised version of posix.
"it's time to stop defending the viability of multithreading today."
Yeah , I'll just side with some guy on slashdot instead of most of the rest of the computer industry.
Not.
"How about you? Under your coding paradigm (whatever it is), do you have some magic method of proving that there are no leaks? "
No, but I wouldn't be so bloody arrogant as to state that I never have.
"is easily solved by using a vector of char to hold the packet's contents"
Err why would I ever want to do that? You think I want to add one character at a time?? And how exactly would I get the internal pointer to use in a read()? Either you've never done network coding or you're just an idiot.
"It's a matter of the compiler taking those libraries and totally fucking with their intended purpose because the language spec lets them and it can improve optimizations."
Yeah , because adding the "volatile" keyword is such a chore.
"I'm glad idiots have opinions."
Me too , and when you get an opinion that makes sense instead of talking out your arse and finding some non example that you've obviously desperately searched long and hard for on goodle, get back to me.
"I've used an embedded language nesC"
Let me guess , written by your professor for your CS101 beginners course.
"shared memory access possible across multithreaded applications is something that C does not currently have a resource for."
Err , I suggest you check out shmget(), shmat(), shmctl() and every other SysV shared memory API function. Also mmap() is rather useful with threads.
Also I'd be interested to know what the interpreter or compiler for Erlang is written in.
Every little niche language has its fanboys, especially in the web development world (no idea why , maybe the sort of people who do web development are more excitable than other coders) and ColdFusion is no exception. So there will be lots of "noise" about it on the internet and this is what this guy is picking up with his stats.
"I have not coded a memory leak or buffer overrun in C++ in over six years."
That you know of.
"The best way to avoid overflowing raw buffers is to not use raw buffers. Use the containers. When you think you can't, think harder."
yes , nice soundbite , but in the real world things arn't always that simple. For example in network data processing you might have to read a packet header , check the size then allocate enough memory for the packet and read it in mapping a number of structure pointers onto the character buffer. Try doing that in any efficient way using the STL.
"At the moment, the C language standard is simply broken for multithreading"
Total BS. The pthreads library works and it works well and so do the equivalent libs on MS Windows. Just because you might find it hard means nothing.
"suitable language for multithreading. It's built into the language itself, like garbage collection is."
You mean it makes it easy for novices. Oh incidentaly , what language do you think the Java VM is written in? Java? Bzzzt , wrong. Its C and assembler. So how do they manage to get the threads working then? It must be magic!
Something else you might want to note is that some problems are best solved by multiprocess rather than multithread , and for that , really Java sucks badly.
".I know it can be done, but C is hard to program for a single core"
I think the translation of that is "I find C hard to program" since single core processors have been the default for most people using C for the last 20 or so years!
"Multicore support may take it over the edge."
Err why? You think programming multicore in C is hard , try it in assembler. At least with C you can always take the easy option and use threading libraries.
Most people use the STL just for dynamic arrays and maps. If you're a half decent programmer its not too hard to role your own (though admittedly a nuisance to have to do so). So no , I wouldn't say knowing the STL is a minimum requirement for programming in C++, in fact for many years before the STL came along C++ chugged along quite happily without it.
"A CD is laughably simple technology, an engineer 100 years from now will build a player (in a way that may not look anything like our current players) in no time at all"
Rubbish. For a start CD players are not simple devices otherwise Edison would have invented them. (Just because something is now a commodity item doesnt mean anyone could build one from scratch). If you;re uncomvinced go study the maths on auto focusing an pit tracking lasers, not to mention D/A conversion, reed solomon error corection etc.
Secondly , skills are lost over time. Try finding someone now who could build a decent siege engine or longbow that would be good enough to fight a medieval battle. Hell , even finding someone these days who can rebuild steam engines is tough!
So in 100 years time, building a CD player from 1st principals could well be a tough call!
At that alititude you're for all intents and purposes in a hard vacuum. There would be no oxygen for the engines and even more worrying , no air for the wings or tail to work with. Even if it could get up that high using a rocket booster it would just tumble out of control.