Point 1: "evaluating to true when the first operand and the second operand point to different memory locations"
The patent appears to cover a single operator (in BASIC, but that is an aside) which does JUST a comparison of whether the 2 operands in fact reside at the same memory address. (e.g. if they were 2 references to instances of the same class, it will tell you if they are in fact references to the same instance of that class)
The C operator != in fact tells you if 2 operands share the same VALUE. This is a different concept, though in the case of pointers you could use it to perform the same test as above. != is NOT an operator with that use as its sole purpose.
Point 2: "When I compare the value of pointers, I'm comparing what memory address they point to... got that? Ok, so when I compare two pointers using != I'm testing that they don't point to the same memory adddress... ok?"
When you declare a pointer (to anything) in C, you in fact declare some form of integer; the exact type varies with your compiler and OS, but its just a NUMBER. When you use the != (or any other logical conparison operator) with that variable, you are in fact just comparing 2 numbers to each other. If you have written your program well, you may in fact be comparing 2 memory addresses, but consider that this is valid C code, and is using the != comparator on two "pointers":
int x = 3000; void *a = void *b = x;
int r = (a != b);
Depending on your choice of number to put in x, you might even manage to get a "true" result from that.
Your knowledge of how pointers actually work seems a tad lacking. You probably think there are no pointers in Java too...
I don't know about you lot, but to me, while its less-huge than current CRTs, 16-inches is not "thin".
YMMV, obviously.
(from TFA: "A 30-inch-tube television from Samsung Electronics will be about 16 inches thick, deeper than a flat panel set but about the same size as the typical stand on a flat-panel television, a Samsung executive said.")
"Google still has a fair use right to your images. They are reduced resolution images and therefor legal for non-commercial use."
FYI; nothing google does is "non commercial".
Even the stuff they let out "for free" serves to funnel their adverts to you, which is their source of revenue. i.e. it is a commercial activity.
Ergo; their use of other people's data (or data ABOUT other people's data, such as a thumbnail of someone else's copyright imagery) is in NO WAY non-commercial.
" I guess Google must not know that Linux has now outpaced desktop installs vs Mac's.."
What google knows is that most Linux desktop installs are downloaded gratis, installed gratis and that the owner/user likes/is interested in "gratis". I'd suggest that many of the machines are home-built not bought-built too?
OS X, OTOH costs money, and only really (Pear notwistanding/not useable) runs on hardware that has to be paid for (pre-built) at the same time as the OS.
Think about it; User interested in free-stuff / cost savings vs User who paid the Apple premium.
Where would _you_ rather vector a global ad-network to??? User who
"But government's meddling in what businesses can pay to each other seems wrong to me."
(I'm not American, nor in America, thank goodness) A previous poster stated that the law prevents the station from recieving inducement and _not disclosing it_ to the listeners. The law doesn't preclude the inducement, just the concealment of "sponsored" playlists.
i.e. it prevents corruption.
This is, in general, a good thing. In the UK, this is why extended "infomercials" have to bear a banner telling you that they are an "advertisement feature"; to prevent the credulous masses from thinking they are getting unbiased information, when in fact they are getting neither (not unbiased, probably not information either)
If you make the program crash, it has ceased processing in a (relatively) short time. You've had a window of opportunity, certainly, but once it crashes its closed.
On the other hand, if you can overflow a buffer and write data into areas that the program will continue to USE...badness ensues.
Methinks you may have "did so well in this" partly backward... (IE is, after all, watertight like a sieve, but its main flaw is that a compromised IE means a compromised windows PC.)
Of course, a really stable and robust program will do neither of these things; it will simply inform you that you fed it garbage, no over-run, no crash, no page.
A company can be said to be "bored" of something once it cannot see any further route to profit through further effort.
Bored as in "had enough of this now".
The rest of the world can be said to be not bored of it, whilst there are ANY people out there who see a point in further work on something (and that generally means while anyone is still using it)
My point (that you bimbled past with your nose in the air) was that IBM don't want to support it anymore (they are "bored" with it), but that they realise that it is not unused (i.e. the WHOLE of the rest of the world isn't "bored" with it), so by opening it, they sidestep the "its now unsupported and we rely upon it, you horrible company" problem, whilst also getting to walk away from it...
(they also get to be the nice "we open source things, and give back to the communnity" company - at the sole cost of no longer maintaining their legacies)
"My point was just that it would be nice to have it so I didn't need a new table for every single thing I wanted multiple references of in order to avoid tons of sql calls to different tables slowing down our webserver."
That sentence tells me instantly that your _really_ seriously have misunderstood the RDBMS paradigm.
Use a table each for: client, address, phone, product
RELATE between these tables to build your whole datum.
i.e. you get client ID to lock you client, you then query for ALL addresses for the client (you can mark one as primary), same for phone numbers (though they may or may not be collated to an address), then query for all that client's products.
Hell, in our DB, the "product" table has 3 fields:
this allows different types of product to store different sets of information (e.g. dvd and videos have their rating, joysticks do not) you can still query "SELECT DISTINCT type FROM product WHERE id = 'code';" to tell you what bits of info are available for a given product, so you can display them.
Our DB handles multiple vendors for products, so there is a "vendor" table with their details. Each vendor can set their own price for any product, so there is an "offer" table which relates a product, a vendor and the actual price...
Building you final data from multiple tables is how you use RDBMS systems, trying to avoid that is like saying "I'm programming my computer, but I'd like to avoid using the keys with letters on them".
You could learn the BF programming language... Or you could do things properly:)
----------
"Alternativly, is there a way to do that so that you can do it with multiple tables but with a single query?"
"But I rarely learn anything about my system by having it work all the time."
It all depends if you have something better than "making it work" that you actually want to get done with your computer.
Personally I firmly moved in to the opposite camp to yours this year; I need and want my computers to be TOOLS now. I have 0 tolerance for them needing tweaking for things like wheel-mice, or more specifically in my case, no time to learn how to recompile the kernel just to install video drivers. (the secret shame of linux...)
Slashdot Mirror
"Unless field_name is a pointer your SQL example is wrong though."
I was "pointing" out that SQl has an "operator" called "IS NOT" not that it did the same thing.
int x = 3000;
void *a = &x;
void *b = x;
int r = (a != b);
this (void asterisk a equals ampersand X semicolon) did not come through well...
Point 1:
"evaluating to true when the first operand and the second operand point to different memory locations"
The patent appears to cover a single operator (in BASIC, but that is an aside) which does JUST a comparison of whether the 2 operands in fact reside at the same memory address. (e.g. if they were 2 references to instances of the same class, it will tell you if they are in fact references to the same instance of that class)
The C operator != in fact tells you if 2 operands share the same VALUE. This is a different concept, though in the case of pointers you could use it to perform the same test as above. != is NOT an operator with that use as its sole purpose.
Point 2:
"When I compare the value of pointers, I'm comparing what memory address they point to... got that? Ok, so when I compare two pointers using != I'm testing that they don't point to the same memory adddress... ok?"
When you declare a pointer (to anything) in C, you in fact declare some form of integer; the exact type varies with your compiler and OS, but its just a NUMBER. When you use the != (or any other logical conparison operator) with that variable, you are in fact just comparing 2 numbers to each other. If you have written your program well, you may in fact be comparing 2 memory addresses, but consider that this is valid C code, and is using the != comparator on two "pointers":
int x = 3000;
void *a =
void *b = x;
int r = (a != b);
Depending on your choice of number to put in x, you might even manage to get a "true" result from that.
Your knowledge of how pointers actually work seems a tad lacking. You probably think there are no pointers in Java too...
That's "does not have the same value as", rather than "is not the same thing as".
SQL has "WHERE field_name IS NOT NULL" though...
http://news.bbc.co.uk/1/hi/programmes/this_world/3 754310.stm
Hmmm?
Refresh rate. :)
Colour reproduction.
Viewable angle.
Brightness
Contrast
Difficulty to knock over
I wouldn't: my 28" flat-screen, wide-screen "fat" CRT television is a whopping... 22" deep.
Wow; lose 6" (27%) and suddenly its "ultra-thin"? I think not.
BTW: they're televisions, not monitors people. And it didn't say HDTV either, so just the NTSC/PAL resolution, making it even LESS impressive.
I don't know about you lot, but to me, while its less-huge than current CRTs, 16-inches is not "thin".
YMMV, obviously.
(from TFA: "A 30-inch-tube television from Samsung Electronics will be about 16 inches thick, deeper than a flat panel set but about the same size as the typical stand on a flat-panel television, a Samsung executive said.")
" First of all, HR 2391 doesn't make it criminal to "skip commercials".
It's meant to disallow technologies that bypass commercial and advertising content explicitly"
Not read the proposed law, but...
Some things immediately spring to mind:
Pop-Up-Blocker (technology designed to bypass advertising - paid for advertising placement no less)
Spam-Filter (technology designed to bypass advertising, though not paid-for in the same sense)
Given the current US trend for "scatter gun laws" (DMCA? PATRIOT?), what chance that these technologies in fact WILL come under this law's auspices?
"iPods sell like hotcakes despite being not free."
iPods sell like hot-cakes because they work with free. If they didn't, they wouldn't.
"Google still has a fair use right to your images. They are reduced resolution images and therefor legal for non-commercial use."
FYI; nothing google does is "non commercial".
Even the stuff they let out "for free" serves to funnel their adverts to you, which is their source of revenue. i.e. it is a commercial activity.
Ergo; their use of other people's data (or data ABOUT other people's data, such as a thumbnail of someone else's copyright imagery) is in NO WAY non-commercial.
" I guess Google must not know that Linux has now outpaced desktop installs vs Mac's.."
What google knows is that most Linux desktop installs are downloaded gratis, installed gratis and that the owner/user likes/is interested in "gratis". I'd suggest that many of the machines are home-built not bought-built too?
OS X, OTOH costs money, and only really (Pear notwistanding/not useable) runs on hardware that has to be paid for (pre-built) at the same time as the OS.
Think about it;
User interested in free-stuff / cost savings
vs
User who paid the Apple premium.
Where would _you_ rather vector a global ad-network to???
User who
We cannot comment on the report, because we cannot read the report; because we have /.'ed the server.
Oh bitter, bitter irony!
Ask yourself these 2 questions about FF and then IE...
How many times have you heard (directly) of someone's machine being infested with 'sploits and spyware through that browser?
How many times have YOU found something slightly suspicious on your machine due to that browser?
Which browser came out as "less secure"?
Security flaws are One Thing, actual in-use live exploits of vulnerabilities are Quite Another.
Plus;
get FF backdoored, browser fucked.
get IE backdoored, COMPUTER fucked.
Hrmm...
"But government's meddling in what businesses can pay to each other seems wrong to me."
(I'm not American, nor in America, thank goodness) A previous poster stated that the law prevents the station from recieving inducement and _not disclosing it_ to the listeners. The law doesn't preclude the inducement, just the concealment of "sponsored" playlists.
i.e. it prevents corruption.
This is, in general, a good thing. In the UK, this is why extended "infomercials" have to bear a banner telling you that they are an "advertisement feature"; to prevent the credulous masses from thinking they are getting unbiased information, when in fact they are getting neither (not unbiased, probably not information either)
time to add a "delete post" operation to /.
Um...
If you make the program crash, it has ceased processing in a (relatively) short time. You've had a window of opportunity, certainly, but once it crashes its closed.
On the other hand, if you can overflow a buffer and write data into areas that the program will continue to USE...badness ensues.
Methinks you may have "did so well in this" partly backward... (IE is, after all, watertight like a sieve, but its main flaw is that a compromised IE means a compromised windows PC.)
Of course, a really stable and robust program will do neither of these things; it will simply inform you that you fed it garbage, no over-run, no crash, no page.
A company can be said to be "bored" of something once it cannot see any further route to profit through further effort.
Bored as in "had enough of this now".
The rest of the world can be said to be not bored of it, whilst there are ANY people out there who see a point in further work on something (and that generally means while anyone is still using it)
My point (that you bimbled past with your nose in the air) was that IBM don't want to support it anymore (they are "bored" with it), but that they realise that it is not unused (i.e. the WHOLE of the rest of the world isn't "bored" with it), so by opening it, they sidestep the "its now unsupported and we rely upon it, you horrible company" problem, whilst also getting to walk away from it...
(they also get to be the nice "we open source things, and give back to the communnity" company - at the sole cost of no longer maintaining their legacies)
Or possibly:
1; we're bored with this
2; rest-of-world is not bored with this
3; open
Gotta love the download instructions, with image of IE download dialog.
.exe files straight off the page..."
They should add "or if your browser is slightly security aware, and doesn't allow you to run
How sure are we they didn't sub-contract writing this to MS?
"My point was just that it would be nice to have it so I didn't need a new table for every single thing I wanted multiple references of in order to avoid tons of sql calls to different tables slowing down our webserver."
:)
That sentence tells me instantly that your _really_ seriously have misunderstood the RDBMS paradigm.
Use a table each for:
client, address, phone, product
RELATE between these tables to build your whole datum.
i.e. you get client ID to lock you client, you then query for ALL addresses for the client (you can mark one as primary), same for phone numbers (though they may or may not be collated to an address), then query for all that client's products.
Hell, in our DB, the "product" table has 3 fields:
id, type, value
products are stored thus:
"code", "name", "product name"
"code", "platform", "product platform"
"code", "rrp", "product rrp"
"code", "image", "product image"
etc.
this allows different types of product to store different sets of information (e.g. dvd and videos have their rating, joysticks do not)
you can still query "SELECT DISTINCT type FROM product WHERE id = 'code';" to tell you what bits of info are available for a given product, so you can display them.
Our DB handles multiple vendors for products, so there is a "vendor" table with their details. Each vendor can set their own price for any product, so there is an "offer" table which relates a product, a vendor and the actual price...
Building you final data from multiple tables is how you use RDBMS systems, trying to avoid that is like saying "I'm programming my computer, but I'd like to avoid using the keys with letters on them".
You could learn the BF programming language... Or you could do things properly
----------
"Alternativly, is there a way to do that so that you can do it with multiple tables but with a single query?"
Oh dear god! Go back to Access.
"But I rarely learn anything about my system by having it work all the time."
It all depends if you have something better than "making it work" that you actually want to get done with your computer.
Personally I firmly moved in to the opposite camp to yours this year; I need and want my computers to be TOOLS now. I have 0 tolerance for them needing tweaking for things like wheel-mice, or more specifically in my case, no time to learn how to recompile the kernel just to install video drivers. (the secret shame of linux...)
20 years from now, we'll have discovered there's a natural grow/shrink cycle we never knew about...
"It also makes me wonder what enthusiasts (like those here on Slashdot) see in Apple."
:(
Simple; their stuff does its job, its job being simple reliable function. Requiring 0 fettling.
Leaving me free to expend my fettling time on things that need it, and things that I don't need constantly working (i.e. not in mid-fettle limbo)
Wintel/WinAMD cannot do this; I spend too long hunting spyware/virus scanning/updating.
Linux cannot do this; I have to work out how to do too much (i.e. I want video drivers; recompile kernel - doh!)
For me, apple is a return t the happy, happy days of the Amiga - a machine that comes in a box, and once out of the box, simply WORKS.
I miss my Amiga
Sony have a history of thinking they can buck the trend, and finally having to give in:
Betamax, dropped.
Atrac, beaten.
CD-Protection, discardeed.
Blu-Ray? Next against the wall?
You'd think a company that can do some things so well, could learn from its history.