MOO-cows Mailing List Archive

[Prev][Next][Index][Thread]

Re: ADV-PROG Re: Defining New Error Codes? [SERVER]



Jay Carlson, who never wants flat text, wrote:

>>   (#-1, #-2, #-3 are already taken, and on E_MOO, I already have #-4
>>     defined as $this for the parser.  You mainly just want to use a
>>     negative object number here that is less than #-3 and not used by
>>     anything else (nothing in a standard lambdacore uses anything less
>>     than #-3))
>
>Except for connections not yet connected to a player object---the ones
>that #0:do_login_command deals with.  They start at, I think #-5 and
>proceed down to negative infinity as new connections come in.

Using Minimal.db, I tested this and found that the inital connection comes
 in as #-2.  I suspect that at -(2^31), they wrap around to +(2^31).
Anyway, my point was that there isn't anything in lambdacore that has hard
 coded refs to negative object numbers less than #-3, in fact, any code that
 _is_ using hard coded refs to negative object numbers should be using
 $failed_match, $ambigious_match, and $nothing anyway, so you should be okay
 to define, as core refs, anything you want and not get any conflicts.
$sys:do_login_command and the entire login stack only use the player object 
 before login in notify()s, so no conflicts there. mmh...

>> Anyone for frobs? (thereby allowing you to overload typeof() and account for
>>  this) :) :) :)  But let's not get into that.  (Check the archives).
>
>...my feelings on this are in the archive...

I, for one, know. :)
For the uninformed, check it out at:
http://shrike.depaul.edu/~abakun/moomail/
  ______                              __
    /   /  Andy Bakun     _/_      / /  `  /)  /)       _/_
 --/   /_  , , , __.  __  /  _  __/ /--   //  //  __,_  /  _
(_/   / /_(_(_/_(_/|_/ (_<__</_(_/ (___, //__//__(_) (_<__/_)_
  How much head could a bonehead bone   />  />
    if a bonehead could bone head?     //  //
  http://shrike.depaul.edu/~abakun/   </  </  




Home | Subject Index | Thread Index