Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ucbcad!ucbvax!ucsfcgl!pixar!unicom!physh From: physh@unicom.UUCP (Jon 'Quality in - Quantity out' Foreman) Newsgroups: comp.unix.xenix Subject: Re: nethack 2.2 SCO fix and query Summary: Stupid dogname bug that everyone has noticed. Message-ID: <217@unicom.UUCP> Date: 10 Dec 87 03:57:06 GMT References:Reply-To: physh@unicom.UUCP Organization: Halcon Co. et al., via College of Marin in California. Lines: 24 In the article by Jay Mathew Libove, he writes: > >My dog starts out with a null name, but "fight.c" >believes (lines 465-475 approximately) that there is a name there, and >until I name (Call) my dog something, if I walk in to him I see >"You stop to avoid hitting ." A minor nuisance at worst; anyone have >a fix for it? ---- Here at College of Marin, there is a fictitious (to everyone except us) dog who lives in our VAX and would "bark" at the console. Every so often, he would have to go, and since he lived in the memory controller, his business would cause a "mcr0: soft ecc" warning (it conducts you see...). This dogs name was "Foobar". So to fix the bug I changed the definition of dogname in dog.c thus: char dogname[63] = { "Foobar" }; So now the dog has a default name, which works just fine. -- {ucbvax,hoptoad}!\ ~~~~~~~\~~~ That's spelled {lll-lcc,hplabs}!well!unicom!physh Jon }() "physh" and {ptsfa,dual}!/ / pronounced "fish".