Re: CHOOSE:FEAT=xxxx, documentation not updated?
- I understand that the converter is limited in scope and I have no problem with that.
I think the details are better discussed in the other thread about the converter in the general PCGen group.
--- In PCGenListFileHelp@yahoogroups.com, "thpr" wrote:
> So yes, the documentation does not correctly tag CHOOSE:FEAT= as being deprecated. We need to get that updated.
> It looks like you have also found a bug in the converter, though I'm unsure why that wasn't noticed as we converted our core datasets. Perhaps we were using a different CHOOSE in Martial Weapon Proficiency?
> We also make sure to convert away from deprecated tokens in any given release, because there is no guarantee that the converter in the next release will be able to read that deprecated token. We only can guarantee their processing for one major release as a deprecated token. So it's best to load without any deprecation errors before you try to move to a new version. (Having said this, the breakage of the converter or the live code not being able to "go back in time" sufficiently is rare, but the policy that we only HAVE TO support it for one release is pretty clear)
> The reason the converter needs to ask is that it is not saving information (nor looking up information) while it does a conversion. It only converts one token at a time... so it's not quite bright enough to "figure it out on its own". (Note that the live code in 6.0.0 CAN figure it out, but it has to do it in two passes - one loading the data to a temporary location saying "This was a CHOOSE:FEAT=" and then after that is complete, by looking up the target feat and figuring out what the CHOOSE was... Someday we will have a smarter converter, but we aren't there today.
> If someone really wants the explanation for why we the prefix is necessary, I can explain it, just want to make sure it's valuable effort.