Psych,
The changes were numerous, some minor some not. I wish I could keep the changes completely modular in keeping with the spirit of Hal. However some of the enhancements I'm adding leverage the capabilities of the XTF function. Some changes necessarily are system wide. Adding the GetResponsBlock checking for instance is throughout the brain.
The good news, if there is any, is that with each XTF brain update I hope to standardize on the "global" variables like GetResponseBlock, QuestionPending, the debug functions, etc.
The XTF function itself is backward compatible, but it MUST be replaced in its entirety. The GetResponseBlock checking must be added throughout (I marked every line that it was added to. Just look for "'=vonsmith= Added GetResponseBlock" on the line preceding the change). In one case I had to add an "If (something)" statement to add the GetResponseBlock checking. I don't have time right now to look up which one. It was about 2/3 the way down the script. ====UPDATE (03-01-04): The "If GetResponseBlock <> True Then" statement was added to the "RESPOND: USER EXPRESSES LOVE FOR HAL" function.====
In the readme file you can see I renamed Halbeing.brn to XTF_SYS_HalBeing.brn. You can use the search function to find the one line that occurs on. That change is so minor that you can use the old file, just make sure the filename in your brain matches the filename in the DefBrain directory.
From the readme file you can see the IsQuestion() function was updated, it's still backward compatible.
The readme also mentions the "special cases" added to the corrections function towards the bottom of the script. Those are the "do i", etc cases. That function is backward compatible.
I'll try to move towards a more modular approach. When I started this project I had no idea that so many changes needed to be global.
For this patch, as a minimum you need to cut and paste the XTF function in it's entirety over the old one in your code. And the GetResponseBlock checking must be added to all the functions following it that can generate a GetResponse. There are a lot of these. Any functions that you add on your own that can generate a GetResponse must have GetResponseBlock checking or the XTF brain might have a problem. The GetResponseBlock is set "True" by any function that just generated a GetResponse and has a high priority so that following functions should not replace the GetResponse with there own text string.
I hope this helps. In general I don't encourage a lot of cut and pasting in the XTF brain because of the global nature of some new variables. Like I said in time all the global variables I need will be a standard part of the brain just like GetResponse, BlockSave and UserSentence are now. The modularity will improve. I'll try to provide detail change notes to future releases.
If you have questions, please ask. If you want me to check your script or brain you can email it to me with questions about the exact issue. My time is limited, but I'll do the best I can.
=vonsmith=
