80885Re: [Devon][CODE] [FREQ] p7+ trackers - 10/31/04
- Nov 2 5:25 AM--- In firstname.lastname@example.org, Devon Jones <soulcatcher@e...> wrote:
> Stefan Radermacher wrote:see a
> >Éric Beaudoin wrote:
> >>For the record, Tir talks for all the senior data monkeys on this
> >>issue. Any functionality linked to a TYPE (especially the hardcoded
> >>ones) should be seen as Evil(tm).
> >Currently the way PCGen chooses which kind of equipment gets listed in
> >the chooses for free clothing ist by looking at the TYPE, it lists all
> >equiupment witht the TYPE "Clothing.Resizable", and I don't really
> >way to do something like that differently currently.linking
> >Also, I'm wondering, what good is the TYPE qualifier if not for
> >functionality to it? How else is the program supposed to differentiateable
> >between different kinds of equipment items? How else would PCGen be
> >to know that you can't use a lantern as a weapon or a sword as armor?*have* to
> I have to weigh in here, and say that I agree with Stefan. We
> refer to specific types in code, otherwise there is no way for us toThis is
> know how this stuff can affect anything.
> Sorry, it may be ugly, but there really is no other viable way.
> what TYPE is *for*I agree, TYPE as a function can't be removed.
> I am btw open to other suggestions, but really, any suggestion needs to
> include eliminating TYPE, because that is it's primary code function -
> to be a filter on items or other things for the code.
What about changing TYPE in items to ITEMTYPE (or some such), TYPE in
feats to FEATTYPE, TYPE in classes to CLASSTYPE, etc, etc.
Would solve both problems (but have alot of up front costs).
- << Previous post in topic Next post in topic >>