User Name:


Forgot your password?
Vote for Us!
Nov 28, 2018, 10:10 am
By Keirath
First Immortal
Oct 12, 2018, 12:02 pm
By GatewaySysop
Bug in do_climb( )
Jun 5, 2018, 5:31 pm
By joeyfogas
question on overland code
May 31, 2018, 10:03 am
By joeyfogas
KaVir's Protocol Snip
May 15, 2018, 7:57 pm
By joeyfogas
tintin++ ogg sound player script for linux
Author: Robert Smith
Submitted by: Vladaar
6Dragons ogg Soundpack
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.4
Author: Vladaar
Submitted by: Vladaar
LoP 1.46
Author: Remcon
Submitted by: Remcon
LOP 1.45
Author: Remcon
Submitted by: Remcon
Users Online
CommonCrawl, Bing

Members: 0
Guests: 8
Newest Member
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Codebases » SWFOTE FUSS » Exit_info and extended bitvec...
Forum Rules | Mark all | Recent Posts

Exit_info and extended bitvectors
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 Jan 24, 2008, 2:17 pm
Go to the top of the page
Go to the bottom of the page

JoinedApr 14, 2005

So, I converted exit_info to extended bitvectors. I've converted all the code, but one pice. I am stuck here.

proom->exflags[x] = eroom->exit_info;

I can't seem to convert that bit to accept extended bitvectors. This is within ships.c in do_makeprototypeship.

Now, I don't even think makeprototypeship works, but I'd like to move in that direction, so I figured this would be a starting point.

Any ideas?

Also, anyone else messed with extended bitvectors much? pros? cons?
Post is unread #2 Jan 25, 2008, 7:11 am   Last edited Jan 25, 2008, 7:13 am by Samson
Go to the top of the page
Go to the bottom of the page

Black Hand
JoinedJan 1, 2002

Without seeing the code, I'm left to assume that proom->exflags[x] is meant to be part of an array of integer values. The extended bitvectors are actually a struct, so you can't assign that to an integer. You'd need to modify the code you're stuck on to give exflags[] the integers it wants, or modify it the other way to make exflags[] hold EXT_BV data instead.

Since Smaug 1.4 and onward come with extended bitvectors by default, pretty much everyone has dealt with them in some way who uses that. Using EXT_BV allows you to go up to 128 bits instead of being stuck with 32. So you have more room to add things you might need. I can't really think of any cons to the system right now, other than the amount of work it takes to convert a set of flags to use it.
Pages:<< prev 1 next >>