The patches were being sent to the Linux Kernel Mailing List a month ago for integrating kernel support for the Cell Processor. Just check the LKML Post from IBM-Deutschland employee Arnd Bergmann.
IBM doesn't tend to release code to the public until it's been through a long approval process;-)
Sorry y'all, but Stevens goofed with this series. He goes over bunches of "upcoming" APIs that just never up and came. Named semaphores? Really? What implementation of UNIX do you know with named semaphores? Come on. The last Stevens book on UNIX IPC and Sockets programming that's pretty universal is APUE.
But even his collection of vaporware APIs is not my biggest problem with this series. It's too long. Far too long. You buy it and think "wow, it's big, I've got a universal reference now." And if you're looking for a pedantic list of distinctions between UNIXes, maybe you have a reference. But if you're looking for that, just read the man pages! The good programming books are the short ones that guide you into your environment--<a href="http://cm.bell-labs.com/cm/cs/cbook/">The C Programming Language</a>; <a href="http://cm.bell-labs.com/cm/cs/upe/">The Unix Programming Environment</a>. Big unenlightening reference tomes of APIs are wastes of paper: the internet is constantly changing. Read the <a href="http://www.ietf.org/rfc.html">RFC</a>' s. That's how you learn how the internet works.
Don't get me wrong. Stevens wrote some good books. APUE is a pretty solid reference (though also <i>too big</i>). TCP/IP Illustrated vol 1 is a really good text for conveying the ideas of networking and the internet protocol -- how they really work. But this series: I don't see it being enlightening to anyone.
The use of "D" will be slightly confusing, as D has commonly stood for deuterium, aka heavy hydrogen - a nucleus of one proton and one neutron circled by one electron. Heavy-heavy hydrogen (tritium - one proton and two neutrons) is what is most useful for fusion research.
It takes the engineers forever to come up with a proper farraday cages to comply with FCC regs on emag emissions; yeah, these designs just throw FCC regs out the window....
The University of Texas Dallas is the ugly little sister of the University of Texas Austin -- you know, the one that smiles at you with her cowboy hat and her two chipped front teeth, the one that no one really wants to date.
I rode through the UTD campus on the way to and from work for about seven months while working for Convex Computer Corporation (now part of HP), located on the north side of campus.
Teaching there is about the equivalent of teaching at the local community college.
The current 3D graphics card industry is extremely cut throat. If a company misses a ship date by a month, They may have lost the entire market for the next year, and with the rate things are changing, that means they're pretty much out of the market. Just look at Cyrix. It was an up-and-comer in the Chip industry, fell a little behind, and slashed itself down to pretty much nothing. It's even worse for graphics cards, because graphics cards have to shove an incredible amount of silicon onto a board for about $20.
Yes, that's right. That's what the computer manufacturers will pay for a graphics card. Twenty Dollars. The Gaming geek who buys his own card for $150 is the *exception* to the rule. All of the real money is made in high-volume. So if the vendors - Packard Bell, Dell, Gateway 2000, Compaq, HP, IBM - pick a card, they will usually get it into systems, test it, and crank out machines for the next 6-12 months with that card as a standard feature. Meanwhile, a product that didn't get picked - if a schedule slipped or a competitor did better with resources, misses the boat and all of that Research and Development is wasted. The card cannot be sold, for by the time the next window comes around, the card is obsolete.
So, if a video card manufacturer believes that they may be able to protect some of their intellectual property by not providing the source for its drivers, then I believe we as a community must accept that decision. For they are having a tough enough time as it is. No reason to give the competitor who may put you out of business an edge.
all right, I know this is slightly off topic, but *why* did you happen upon the variable name 'eger'? It is the name of a well-known town in Hungary, and a common last name of people from the area.
There is a standard problem with current 32 bit libraries and the UNIX functions ctime(), gmtime() and localtime(). They all take an argument of data type time_t which represents calendar time. When interpreted as an absolute time value, it represents the number of seconds elapsed since 00:00:00 on January 1, 1970, Coordinated Universal Time (UTC).
When time_t is represented as a 32 bit integer, this representation fails at about 2038. This limitation should disappear, however, when the libraries are replaced with 64 bit versions. This is by no means any problem with C++ itself.
Slashdot Mirror
IBM doesn't tend to release code to the public until it's been through a long approval process ;-)
A move against bloggers would likely be stopped by the Supreme Court as a violation of free speech rights. Blog = Speech
still in beta, but it finds pizza ;-)
Sorry y'all, but Stevens goofed with this series. He goes over bunches of "upcoming" APIs that just never up and came. Named semaphores? Really? What implementation of UNIX do you know with named semaphores? Come on. The last Stevens book on UNIX IPC and Sockets programming that's pretty universal is APUE.
But even his collection of vaporware APIs is not my biggest problem with this series. It's too long. Far too long. You buy it and think "wow, it's big, I've got a universal reference now." And if you're looking for a pedantic list of distinctions between UNIXes, maybe you have a reference. But if you're looking for that, just read the man pages! The good programming books are the short ones that guide you into your environment--<a href="http://cm.bell-labs.com/cm/cs/cbook/">The C Programming Language</a>; <a href="http://cm.bell-labs.com/cm/cs/upe/">The Unix Programming Environment</a>. Big unenlightening reference tomes of APIs are wastes of paper: the internet is constantly changing. Read the <a href="http://www.ietf.org/rfc.html">RFC</a>' s. That's how you learn how the internet works.
Don't get me wrong. Stevens wrote some good books. APUE is a pretty solid reference (though also <i>too big</i>). TCP/IP Illustrated vol 1 is a really good text for conveying the ideas of networking and the internet protocol -- how they really work. But this series: I don't see it being enlightening to anyone.
The use of "D" will be slightly confusing, as D has commonly stood for deuterium, aka heavy hydrogen - a nucleus of one proton and one neutron circled by one electron. Heavy-heavy hydrogen (tritium - one proton and two neutrons) is what is most useful for fusion research.
haven't these guys heard of ogg and theora?
It takes the engineers forever to come up with a proper farraday cages to comply with FCC regs on emag emissions; yeah, these designs just throw FCC regs out the window....
The University of Texas Dallas is the ugly little sister of the University of Texas Austin -- you know, the one that smiles at you with her cowboy hat and her two chipped front teeth, the one that no one really wants to date.
I rode through the UTD campus on the way to and from work for about seven months while working for Convex Computer Corporation (now part of HP), located on the north side of campus.
Teaching there is about the equivalent of teaching at the local community college.
Yes, that's right. That's what the computer manufacturers will pay for a graphics card. Twenty Dollars. The Gaming geek who buys his own card for $150 is the *exception* to the rule. All of the real money is made in high-volume. So if the vendors - Packard Bell, Dell, Gateway 2000, Compaq, HP, IBM - pick a card, they will usually get it into systems, test it, and crank out machines for the next 6-12 months with that card as a standard feature. Meanwhile, a product that didn't get picked - if a schedule slipped or a competitor did better with resources, misses the boat and all of that Research and Development is wasted. The card cannot be sold, for by the time the next window comes around, the card is obsolete.
So, if a video card manufacturer believes that they may be able to protect some of their intellectual property by not providing the source for its drivers, then I believe we as a community must accept that decision. For they are having a tough enough time as it is. No reason to give the competitor who may put you out of business an edge.
all right, I know this is slightly off topic, but *why* did you happen upon the variable name 'eger'? It is the name of a well-known town in Hungary, and a common last name of people from the area.
When time_t is represented as a 32 bit integer, this representation fails at about 2038. This limitation should disappear, however, when the libraries are replaced with 64 bit versions. This is by no means any problem with C++ itself.