Re: Direction code problem(1)&(2)

From: Shane Lee (mudmaster@Randor.zzn.com)
Date: 07/08/00


---- Begin Original Message ----

From: Charles Erwin <Mystikarc@aol.com>
Sent: Sat, 8 Jul 2000 17:33:18 EDT
To: CIRCLE@post.queensu.ca
Subject: [CIRCLE] Direction code problem(1)


I use bpl17:
Code is for bpl17:
I recieved this warnign while coding ordinal directions:
objsave.c: In function `Crash_extract_norent_eq':
objsave.c:669: warning: unused variable `obj'

if anyone knows what this means, and can help me please I would
appreciate it.
thank you very much.
the following is a clip of the code and where I got it from:

                 Ordinal Directions for 3.0bpl17 (nw, ne, sw, se) [by
Khalun]

             Posted Saturday, June 17th @ 04:08:57 PM, by Brandon
Brown in
the
            Rooms dept.
            Kkalun writes, "This is what I did to create ne, nw, se,
and sw.
It
            seemed way easier than the other patches for ordinal
directions...."

const char *dirs[] =
{
  "north",
[SNIP]
(there is more which will be in Dir Problem(2)


     +------------------------------------------------------------+
     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     |  http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html  |
     +------------------------------------------------------------+


---- End Original Message ----


First, (I suppose you will get several replies on this one) there is
no need to send patches or snippets, but you might mention the name
and version of it when writing in.
Second, I have no idea why you would be editing the
`Crash_extract_norent_eq' function at all while editing in ordinal
directions, but since you got the warning you might try one of two
things in objsave.c:
1) read the entire `Crash_extract_norent_eq' function and see why you
even have a variable named 'obj' in it anyway. If there are others
coding your source with you, be sure to get with them about any rent
changes they may be making. Remove the variable, which prolley looks
like this;
int obj;

2) replace your existing `Crash_extract_norent_eq' function with the
stock version (back up your existing function first, since you are
only getting a warning and not an error, it means its working more or
less);
void Crash_extract_norent_eq(struct char_data *ch)
{
  int j;

  for (j = 0; j < NUM_WEARS; j++) {
    if (GET_EQ(ch, j) == NULL)
      continue;

    if (Crash_is_unrentable(GET_EQ(ch, j)))
      obj_to_char(unequip_char(ch, j), ch);
    else
      Crash_extract_norents(GET_EQ(ch, j));
  }
}

If this doesn't work, then someone is screwing with your rent files.
Again, this has nothing to do with your current project so the
warning is sorta wierd in the first place.

-FIRE


Get your Free E-mail at http://randor.zzn.com
____________________________________________________________
Get your own Web-Based E-mail Service at http://www.zzn.com


     +------------------------------------------------------------+
     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     |  http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html  |
     +------------------------------------------------------------+



This archive was generated by hypermail 2b30 : 04/10/01 PDT