The AI Engine

well, it's a standard regex actually, though perhaps a little too greppy for the AI Engine.

Sometimes it pays to be very tired and just about to go to bed though - a little lateral thinking has just given me:

what do ([abcdefghijklmnopqrstuvwxyz]+)ists believe (re)

and it works nicely.
I assume in my first one it was trying to match "a", "z" and "-" instead of interpreting the hyphen as a range indicator.
I will indeed cover as many of the non-ists with a plug-in as I can though.

This is weird...apparantly the word "hungry" gets picked up by (adj) but not by (adjartnoun).

I think the Prof recently made it so that (adjartnoun) wouldn't register unless there was actually a noun there.

Ah. Then I guess for this particular keyphrase I'll use ((adj)|(adjartnoun)).

You can't put chrono AI script to "xgoodbye"?

I just don't get the raw mode. You're supposed to put "<?PF raw; ?>" in the keyphrase? Where? In the AI script section? Are you supposed to add something to it? It doesn't work and I don't know why.

It goes in the AI Script field.

It's hit and miss for me too. Raw mode seems to work best for me with (re) keyphrases.

If you have several conditional statements in one line, does it go through them in order, or do only one of them have to be right?

for example,
How's your husband doing? <?PF if (mem-married) is "yes"; if female; ?>

Would that be asked to males who are married or females who aren't married?

I would assume they all have to be right - in the above, it will only ask the question to females who already have the memory married = "yes" stored.

Why aren't OK and okay interchangeable as key phrases? Like yes, yeah and yup are? (or are they, lol)

I thought they were.

I've been using (ok|okay) for a couple of years now. I always presumed that preprocessing changed one to the other, but I could never figure it out. Maybe that would explain why...

Anyhow, (ok|okay) seems to work for me.