🚀 go-pugleaf

In many articles & pieces of e-mail, many people have said something to the
effect of:
>>>Well, this is not exactly an error message, but I crack up everytime I
>>>see "Press ENTER to exit", which exists in several programs I've used.
>> 
>> Huh?
>> 
>> I think something is missing?
> 
>	I think you just failed to get the joke.  "Enter to exit"...  think
>about it.  It shouldn't have to be explained. ;-)

Quite right.  Apparently it was my brain which happened to be missing. 
 Sorry all...


---
 Note: I do not represent my employer or school, & sometimes not even myself.

  Dave Archer  |  Internet: V116...@UBVMS.CC.BUFFALO.EDU      !
               |    Bitnet: V116KZND@UBVMS.BITNET

Well, its not exactly an error message - but the other day we got a
machine from a manufacturer who shall remain nameless - to which I 
wanted to try to port ELK to test out its compiler and also to run
some speed tests (interpreters make interesting benchmarks).  I
ran into some problems (600,000 bytes of error messages in the whole 
thing - but mostly in the X window stuff).  I finally managed to
get the part without X windows to compile (modulo normal problems
with include files and so on, ah, portability).  Ran it.  It
promptly dumped core.  dbx revealed the following (look at the
args to General_Make_Vector) :

$ dbx scheme
Type 'help' for help.
reading symbolic information ...warning: no source compiled with -g

[using memory image in core]

segmentation violation in General_Make_Vector at 0x10011468
0x10011468 (General_Make_Vector+0xac) 90650000         st   r3,0x0(r5)
(dbx) where
General_Make_Vector(0x3f1, 0x6000000, 0x0, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef, 0x100) at 0x10011468
Init_Symbol() at 0x100037fc
Init_Everything() at 0x10000638
main(0x6000000, 0x6000000) at 0x100004e4
(dbx) quit

Tell me thats a coincidence! 

-- 
je...@jupiter.nmt.edu  -- Jeff Putnam, New Mexico Tech, Socorro, NM

je...@nmt.edu (Jeff Putnam) writes:
>General_Make_Vector(0x3f1, 0x6000000, 0x0, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef, 0x100) at 0x10011468

I usually write this constant down as 0x0deadbeef in the source
(OXO is a brandname of a stockcube in England)

>Tell me thats a coincidence! 
No, its a magic number! This one appears in Unix System Five as part of the
Alternate disk sector mapping sanity check. Also present is
0xdeadfeeb as the volume label magic number.
-- 
Here I speak neither for Specialix, nor myself. What you see is all you get.
Jon Brawn, jo...@specialix.co.uk  (or for you bangers: ..!mcsun!ukc!slxsys!jonb)
  ``Once upon a time, not so very long ago, on a network not so very far away''

In article <1990Sep27....@specialix.co.uk> jo...@specialix.co.uk (Jon Brawn) writes:
>Alternate disk sector mapping sanity check. Also present is
>0xdeadfeeb as the volume label magic number.

A core file has the magic number of 0xdeadadb0.  How many other of the
hexajokes are there?

							spl (the p stands for
							poking around core
							dumps, again...)
-- 
Steve Lamont, SciViGuy -- (408) 646-2752 (subject to change at random)
NPS Confuser Center / Code 51 / Naval Postgraduate School / Monterey, CA 93940
"You're okay," said Honeysuckle.  "The dogs like you."
			- Charles Bukowski, "How to Get Published"

In article <1990Sep27.0...@nmt.edu> je...@nmt.edu (Jeff Putnam) writes:
>(dbx) where
>General_Make_Vector(0x3f1, 0x6000000, 0x0, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef, 0x100) at 0x10011468
> ...
>Tell me thats a coincidence! 

  In the same vein, the magic number for a Mach-Object module (on a NeXT)
is 0xfeedface .... 


-- 
 wi...@milton.acs.washington.edu       Seattle, Washington   
     (William Lewis)   |  47 41' 15" N   122 42' 58" W  
"These 2 cents will cost the net thousands upon thousands of 
dollars to send everywhere. Are you sure you want to do this?"

In article <1990Sep27.0...@nmt.edu> je...@nmt.edu (Jeff Putnam) writes:
=> $ dbx scheme
 ...
=> (dbx) where
=> General_Make_Vector(0x3f1, 0x6000000, 0x0, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef, 0x100) at 0x10011468
=> 
=> Tell me thats a coincidence! 

When poking around some data files created by a synthesizer patch librarian,
I discovered that the first 4 bytes were 0xdeadbeef.  A magic number, I
suppose.

I laughed for several minutes.
-- 
     Ken Sallenger / k...@bigbird.csd.scarolina.edu / +1 803 777-9334
     Computer Services Division / 1244 Blossom ST / Columbia, SC 29208

>In article <15...@yunexus.YorkU.CA> shi...@yunexus.YorkU.CA (Paul Shields) writes:
>s...@cs.nps.navy.mil (Steve Lamont) writes:

[re: inventing your own hexajokes]

> 0xb0bd0bbs

Hmmm. You need slack. 's' is not a valid hexadecimal digit on earth.
Maybe it is on Xist.

--
| ben@epmooch.UUCP   (Ben Mesander)       | "Cash is more important than |
| ben%serv...@uokmax.ecn.uoknor.edu |  your mother." - Al Shugart, |
| !chinet!uokmax!servalan!epmooch!ben     |  CEO, Seagate Technologies   |

ben@epmooch.UUCP (Rev. Ben A. Mesander) writes:

|>In article <15...@yunexus.YorkU.CA> shi...@yunexus.YorkU.CA (Paul Shields) writes:
|>s...@cs.nps.navy.mil (Steve Lamont) writes:
|
|[re: inventing your own hexajokes]
|
|> 0xb0bd0bbs
|
|Hmmm. You need slack. 's' is not a valid hexadecimal digit on earth.
|Maybe it is on Xist.

How about
	0xBOBDOBB5
Font dependant I guess..
-- 
Jeremy Fitzhardinge: jer...@ultima.socs.uts.edu.au jer...@utscsd.csd.uts.edu.au 
                             DEATH TO ALL FANATICS!!!