curious -- Is Sellotape to New Zealand what Scotch Tape is to the US?
If so, then their is pretty much invalid by the fact that it's considered a generic term by the public. Kinda like the MS v. LindowsOS case, where MS might lose their on Windows because it's a generic term.
i never thought it was possible to make donatations to letters of the english alphabet! hmmm.......
Re:When comments are more than comments...
on
Pet Bugs?
·
· Score: 1
ok, i just fed the below into gcc 2.96 on rh 7.1:
#include <stdio.h>
// --- jeff was here --- \\ typedef unsigned char uchar; int something (uchar c);
int main () {
something('c');
return 0; }
int something (uchar c) {
printf ("%c\n", c);
return 0; }
bash$ gcc sample.c sample.c:5: parse error before `c' sample.c:14: parse error before `c' sample.c: In function `something': sample.c:16: `c' undeclared (first use in this function) sample.c:16: (Each undeclared identifier is reported only once sample.c:16: for each function it appears in.)
bash$ gcc sample -E
---preprocessed stdio.h, i'm not about paste all 800+ lines---
int something (uchar c);
int main () {
something('c');
return 0; }
int something (uchar c) {
printf ("%c\n", c);
return 0; }
So we see that I was correct (at least for my compiler) in that the \ at the end of the line is removed, then replaced with the contents of the following line, effectively removing the typedef from being compiled.
For verification, I'll remove the \\ from the above and retry--
bash$ gcc sample.c bash$./a.out c bash$
As expected, the only output is the character 'c' followed by a newline.
Re:When comments are more than comments...
on
Pet Bugs?
·
· Score: 1
crap, part of that #include line got eaten thanks to the < and > delimiters on the
Re:When comments are more than comments...
on
Pet Bugs?
·
· Score: 2, Informative
this is a guess...
the back-slash \ at the end of the line indicates to the compiler that the following line is to be considered part of the current line, meaning the compiler (iirc, lexical analyzer) will translate the above to the following:
#include
// tom 7 was here - 1998 \typedef unsigned char uchar; int something(uchar c);
or more precisely--
--preprocessed contents of stdio.h-- int something(uchar c);
so the "bug" (actually a compile-time error) is an undefined token 'uchar,' unless of course, uchar has a definition in stdio.
prior to slashdot's existance, the phrase "flash crowd" was used.
It was the title of a sci-fi short story years ago, in an age where teleportation exists and some major event occurs, causing people from all over teleport themselves to the event, causing a large crowd to appear, only to disappear after the event was over.
In the computing sense, it referred to legit cases of denial-of-service. For example, a "flash crowd" occured on 9/11 when MSNBC.com, CNN.com, etc, were all overloaded with connections from people seeking info on what was going on.
the guy also seems to suggest that Linus is still in college, and makes no mention as to how long Linux has been out there. On top of that, more than just IBM people get paid -- Red Hat comes to mind.
One more crippling bombshell hit the already beleaguered Linux community when MSNBC confirmed that Linux market share has not risen significantly in comparison to others, less than 5 percent of all servers. Coming on the heels of a recent MSNBC survey which plainly states that Linux has lost more market share to Windows, this news serves to reinforce what we've known all along. Linux is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent MCSE comprehensive networking test.
You don't need to be a Kreskin to predict Linux's future. The hand writing is on the wall: Linux faces a bleak future. In fact there won't be any future at all for Linux because Linux is dying. Things are looking very bad for Linux. Red ink flows like a river of blood.
Let's keep to the facts and look at the numbers.
All major surveys show that Linux has steadily declined in market share. Linux is very sick and its long term survival prospects are very dim. If Linux is to survive at all it will be among OS dilettante dabblers. Linux continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Linux is dead.
But I don't understand why they don't require merchants to mask out the card # and other sensitive info on the credit card slips.
IIRC, this topic came up a few months ago. California consumer protection laws require merchants to shield all but the last 4 digits. Dont know what other states (if any) mandates this. I do know that a lot of merchants already do this on their own, often out of a desire to protect their customers, but others are national chains with stores in CA.
You could send a letter of complaint to the restaurant you were at when the busboy got your CCN, telling them about your experience and recommending a system that hides the first 12 digits. Find out if your state has a law like CA's, and if so, mention that. If it turns out there is a law, consider pressing charges for negligence of that law, or inform the state if you dont want to go through with a suit and let them handle it. You might be surprised how they handle it given that $13k was put at stake here.
I'll be an undergraduate senior this fall, and yes, I've thought about asking. I dont know if I'm that serious about it yet, VMs are just one of the few topics running around in my head. If I stay at my current school (Drexel) for grad school, i dont think VMs would make a good topic, whereas parallel systems or reverse engineering would. Though VMs could come integrate themselves into RE. hmmm.....
yes, I'm aware of how to exclude certain tokens from a google search. Unfortunately, one mention of the word "java" in a document (like the review above, or the book's webpage), and the page is eliminated from the result set, leaving behind very little to work with.
I must say I'm pleased to hear about this book. I actually would like to do something with VMs in my upcoming academic life (read: grad school), but am having trouble getting started, nor am sure if this is what i want to study. Every search engine out there returns everything Java for the phrase "virtual machine," which is not exactly what I'm looking for.
i dont know if it's a blacklist or not. I tried copy/paste into the address field and got the same error. Maybe they have something akin to a formkey buried in the URL?
The article talks about hardware changes, including changes to the chip since both Intel and AMD are involved. Could this mean the end of x86-based open source OS's, including Linux and the BSDs?
This sounds like what States' Attorney Steve Kunney put into closing arguments this past week:
Somehow they know better than anyone else what's best for this PC ecosystem. What's good for Microsoft is therefore good for the economy, good for consumers and good for everybody else.
Slashdot Mirror
what about newsforge.com? their site specifically says "The Online Newspaper of Record for Linux and Open Source"
i think i'm gonna have to update the link in my .sig one of these days.
Ya know, CmdrTaco, there are doctors out there that can help you with your depression since the loss of John Entwistle of The Who.
curious -- Is Sellotape to New Zealand what Scotch Tape is to the US?
If so, then their is pretty much invalid by the fact that it's considered a generic term by the public. Kinda like the MS v. LindowsOS case, where MS might lose their on Windows because it's a generic term.
IANAL.
you're still wrong.
#define TRUE 1
#define FALSE 0
that would explain all the firewall hits from 64.28.67.150.
hey, you're right! "Today's Seseme Street has been brought to you by the Letter 'A'"
:-)
Maybe the sponsor will now be WSIF??
i never thought it was possible to make donatations to letters of the english alphabet! hmmm.......
ok, i just fed the below into gcc 2.96 on rh 7.1:
./a.out
#include <stdio.h>
// --- jeff was here --- \\
typedef unsigned char uchar;
int something (uchar c);
int main ()
{
something('c');
return 0;
}
int something (uchar c)
{
printf ("%c\n", c);
return 0;
}
bash$ gcc sample.c
sample.c:5: parse error before `c'
sample.c:14: parse error before `c'
sample.c: In function `something':
sample.c:16: `c' undeclared (first use in this function)
sample.c:16: (Each undeclared identifier is reported only once
sample.c:16: for each function it appears in.)
bash$ gcc sample -E
---preprocessed stdio.h, i'm not about paste all 800+ lines---
int something (uchar c);
int main ()
{
something('c');
return 0;
}
int something (uchar c)
{
printf ("%c\n", c);
return 0;
}
So we see that I was correct (at least for my compiler) in that the \ at the end of the line is removed, then replaced with the contents of the following line, effectively removing the typedef from being compiled.
For verification, I'll remove the \\ from the above and retry--
bash$ gcc sample.c
bash$
c
bash$
As expected, the only output is the character 'c' followed by a newline.
crap, part of that #include line got eaten thanks to the < and > delimiters on the
this is a guess...
the back-slash \ at the end of the line indicates to the compiler that the following line is to be considered part of the current line, meaning the compiler (iirc, lexical analyzer) will translate the above to the following:
#include
// tom 7 was here - 1998 \typedef unsigned char uchar;
int something(uchar c);
or more precisely--
--preprocessed contents of stdio.h--
int something(uchar c);
so the "bug" (actually a compile-time error) is an undefined token 'uchar,' unless of course, uchar has a definition in stdio.
prior to slashdot's existance, the phrase "flash crowd" was used.
It was the title of a sci-fi short story years ago, in an age where teleportation exists and some major event occurs, causing people from all over teleport themselves to the event, causing a large crowd to appear, only to disappear after the event was over.
In the computing sense, it referred to legit cases of denial-of-service. For example, a "flash crowd" occured on 9/11 when MSNBC.com, CNN.com, etc, were all overloaded with connections from people seeking info on what was going on.
the guy also seems to suggest that Linus is still in college, and makes no mention as to how long Linux has been out there. On top of that, more than just IBM people get paid -- Red Hat comes to mind.
er...
like this given the source
It's Official - MSNBC Confirms - Linux Is Dying
One more crippling bombshell hit the already beleaguered Linux community when MSNBC confirmed that Linux market share has not risen significantly in comparison to others, less than 5 percent of all servers. Coming on the heels of a recent MSNBC survey which plainly states that Linux has lost more market share to Windows, this news serves to reinforce what we've known all along. Linux is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent MCSE comprehensive networking test.
You don't need to be a Kreskin to predict Linux's future. The hand writing is on the wall: Linux faces a bleak future. In fact there won't be any future at all for Linux because Linux is dying. Things are looking very bad for Linux. Red ink flows like a river of blood.
Let's keep to the facts and look at the numbers.
All major surveys show that Linux has steadily declined in market share. Linux is very sick and its long term survival prospects are very dim. If Linux is to survive at all it will be among OS dilettante dabblers. Linux continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Linux is dead.
Fact: Linux is dying
...like we're gonna beleive a story like given the source: MSNBC
But I don't understand why they don't require merchants to mask out the card # and other sensitive info on the credit card slips.
IIRC, this topic came up a few months ago. California consumer protection laws require merchants to shield all but the last 4 digits. Dont know what other states (if any) mandates this. I do know that a lot of merchants already do this on their own, often out of a desire to protect their customers, but others are national chains with stores in CA.
You could send a letter of complaint to the restaurant you were at when the busboy got your CCN, telling them about your experience and recommending a system that hides the first 12 digits. Find out if your state has a law like CA's, and if so, mention that. If it turns out there is a law, consider pressing charges for negligence of that law, or inform the state if you dont want to go through with a suit and let them handle it. You might be surprised how they handle it given that $13k was put at stake here.
I'll be an undergraduate senior this fall, and yes, I've thought about asking. I dont know if I'm that serious about it yet, VMs are just one of the few topics running around in my head. If I stay at my current school (Drexel) for grad school, i dont think VMs would make a good topic, whereas parallel systems or reverse engineering would. Though VMs could come integrate themselves into RE. hmmm.....
but anyways, thanks for the suggestion.
yes, I'm aware of how to exclude certain tokens from a google search. Unfortunately, one mention of the word "java" in a document (like the review above, or the book's webpage), and the page is eliminated from the result set, leaving behind very little to work with.
I must say I'm pleased to hear about this book. I actually would like to do something with VMs in my upcoming academic life (read: grad school), but am having trouble getting started, nor am sure if this is what i want to study. Every search engine out there returns everything Java for the phrase "virtual machine," which is not exactly what I'm looking for.
i dont know if it's a blacklist or not. I tried copy/paste into the address field and got the same error. Maybe they have something akin to a formkey buried in the URL?
the fish seems to be floating on it's side at the top of the bowl, so let's try Google's translation instead
The article talks about hardware changes, including changes to the chip since both Intel and AMD are involved. Could this mean the end of x86-based open source OS's, including Linux and the BSDs?
This sounds like what States' Attorney Steve Kunney put into closing arguments this past week:
Somehow they know better than anyone else what's best for this PC ecosystem. What's good for Microsoft is therefore good for the economy, good for consumers and good for everybody else.
the article didnt cover it: how much did he bash single button mice?