DSPRelated.com
Forums

OT Confused VAX programmer

Started by Jerry Avins September 18, 2005
My email server was down for about 8 hours before bedtime yesterday. 
This morning it was back up. In the batch of early mail, I was told 
about the programmer who didn't distinguish Halloween from Christmas 
because OCT 31 is also DEC 25

Jerry
-- 
Engineering is the art of making what you want from things you can get.
�����������������������������������������������������������������������
"Jerry Avins" <jya@ieee.org> wrote in message 
news:Vdednddkwtod7rDeRVn-gw@rcn.net...
> My email server was down for about 8 hours before bedtime > yesterday. This morning it was back up. In the batch of > early mail, I was told about the programmer who didn't > distinguish Halloween from Christmas because OCT 31 is > also DEC 25 >
Somebody ought to put a HEX on him.
You might like this take on a often quoted shakespeare line
2B | !2B = FF

Cheers,
Dave

John E. Hadstate wrote:
> "Jerry Avins" <jya@ieee.org> wrote in message > news:Vdednddkwtod7rDeRVn-gw@rcn.net... > >>My email server was down for about 8 hours before bedtime >>yesterday. This morning it was back up. In the batch of >>early mail, I was told about the programmer who didn't >>distinguish Halloween from Christmas because OCT 31 is >>also DEC 25 >> > > > Somebody ought to put a HEX on him. > >
I don't get the FF part.

"David Kirkland" <spam@netscape.net> wrote in message 
news:Mf2Ye.7723$0u2.1238759@news20.bellglobal.com...
> You might like this take on a often quoted shakespeare line > 2B | !2B = FF > > Cheers, > Dave
You have to think in Hex. In C it would be (assuming an 8 bit data type)
0x2B | !0x2B = 0xFF

Maybe it's just my strange sense of humour - it was funny when I first 
saw it.

Cheers,
Dave

Jon Harris wrote:
> I don't get the FF part. > > "David Kirkland" <spam@netscape.net> wrote in message > news:Mf2Ye.7723$0u2.1238759@news20.bellglobal.com... > >>You might like this take on a often quoted shakespeare line >>2B | !2B = FF >> >>Cheers, >>Dave > > >
David Kirkland wrote:
> You have to think in Hex. In C it would be (assuming an 8 bit data type) > 0x2B | !0x2B = 0xFF
That's the best argument I've seen that the ASCII code for '?' should have been 0xFF. -- Jim Thomas Principal Applications Engineer Bittware, Inc jthomas@bittware.com http://www.bittware.com (603) 226-0404 x536 A great mind thinks alike.
Jon Harris wrote:
> I don't get the FF part. > > "David Kirkland" <spam@netscape.net> wrote in message > news:Mf2Ye.7723$0u2.1238759@news20.bellglobal.com... > >>You might like this take on a often quoted shakespeare line >>2B | !2B = FF
In binary, x | !x = 11111111, where x is any number (C notation). Jerry -- Engineering is the art of making what you want from things you can get. &#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;
Jim Thomas wrote:
> David Kirkland wrote: > >> You have to think in Hex. In C it would be (assuming an 8 bit data type) >> 0x2B | !0x2B = 0xFF > > > That's the best argument I've seen that the ASCII code for '?' should > have been 0xFF.
I like that, but it got to be the way it is so that you could overpunch any character with Code Delete. Jerry -- Engineering is the art of making what you want from things you can get. &#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;
"David Kirkland" <spam@netscape.net> wrote in message
news:WGbYe.7974$0u2.1426644@news20.bellglobal.com...

> You have to think in Hex. In C it would be (assuming an 8 bit data type) > 0x2B | !0x2B = 0xFF
But shouldn't this only be true for bitwise logical negation, i. e. 0x2B | ~0x2B? Example: #include <stdio.h> int main() { unsigned char x; x = 0x2B | !0x2B; printf("%x\n", x); x = 0x2B | ~0x2B; printf("%x\n", x); return 0; } -- write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, & 6.0134700243160014d-154/),(/'x'/)); end
Jerry Avins wrote:

> Jim Thomas wrote: > >> David Kirkland wrote: >> >>> You have to think in Hex. In C it would be (assuming an 8 bit data type) >>> 0x2B | !0x2B = 0xFF >> >> >> >> That's the best argument I've seen that the ASCII code for '?' should >> have been 0xFF. > > > I like that, but it got to be the way it is so that you could overpunch > any character with Code Delete. > > Jerry
You mean the 026 will live forever :{