Modify parse_affix_string() in affixmisc.repy to reject certain AFFIX strings.

[monzum]

parse_affix_string() needs to be changed to reject various AFFIX strings that were acceptable before. For example, previously an AFFIX stack was allowed to have other AFFIX components underneath branching/splitter AFFIXs. This is no longer allowed in our new design.

[JustinCappos]

How does this function know what is classified as a "branching Affix",
etc.?

On Wed, Nov 20, 2013 at 2:35 PM, monzum notifications@github.com wrote:

parse_affix_string() needs to be changed to reject various AFFIX strings
that were acceptable before. For example, previously an AFFIX stack was
allowed to have other AFFIX components underneath branching/splitter
AFFIXs. This is no longer allowed in our new design.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21
.

[monzum]

Unfortunately there is no way to identify a branching AFFIX. I will have to give it some thought and come up with a good solution. My initial though was to check if the arguments of the AFFIX are AFFIX stacks, however I don't believe this is a viable solution.

[JustinCappos]

Right. So I think part of being an Affix is correctly serializing /
deserializing.

Justin

On Wed, Nov 20, 2013 at 3:44 PM, monzum notifications@github.com wrote:

Unfortunately there is no way to identify a branching AFFIX. I will have
to give it some thought and come up with a good solution. My initial though
was to check if the arguments of the AFFIX are AFFIX stacks, however I
don't believe this is a viable solution.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-28929213
.

[monzum]

AFFIXs themselves should correctly serialize/deserialize themselves. Users can still provide a bad AFFIX string when initially building the AFFIX stack. I propose that we have a wiki page or README file that educates users/developers of proper AFFIX stacks and what to do or not to do.

[JustinCappos]

They "should" serialize and deserialize, but we don't need to (and most
likely can't) enforce this. It's much like other semantic properties.

On Wed, Nov 20, 2013 at 5:24 PM, monzum notifications@github.com wrote:

AFFIXs themselves should correctly serialize/deserialize themselves. Users
can still provide a bad AFFIX string when initially building the AFFIX
stack. I propose that we have a wiki page or README file that educates
users/developers of proper AFFIX stacks and what to do or not to do.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-28937753
.