|
Post by George on Mar 7, 2024 9:19:06 GMT -5
Robert: I have the basic parser re-written, and the underlying manipulators (Search, Change, Join etc.), but each Primary command needs tweaking to accept the new method. In most cases it's fairly trivial, but some commands are quite a struggle. I'm working through them A-Z and am tackling LOCATE right now. It's gotta be the worst one so far, over 50 keyword type parameters mixed in with some having trailing numeric operands. It's a nightmare.
I'd like to respecify and re-write it, but we're stuck with what we've created.
Interesting during all this, I've found several places where the Doc is incomplete, or has conflicting information, so these are corrected as I go.
Fun, fun, fun!
George
|
|
|
Post by George on Mar 1, 2024 14:47:41 GMT -5
Robert: That's why I have to check carefully. Some commands are issued internally with secret Kwds, for various reasons. It's not a big problem, just something to watch for. These internal Kwds will NEVER be documented in HELP.
George
|
|
|
Post by George on Mar 1, 2024 11:21:56 GMT -5
Robert: Could be interesting. First I'll get things working to handle the existing syntax (which is mandatory).
I'm working through the commands now and each one seems to require some modification/correction to the parser. It shows just how many internal 'exceptions to the rule' have been introduced over the years. I've also found code supporting operands that aren't even documented. Those I have to watch for as some are 'internal only' and probably can't be just tossed out.
George
|
|
|
Post by George on Feb 29, 2024 16:19:59 GMT -5
The forum has been pretty quiet lately, but just as an FYI, I have been active in the background.
Because SPFLite has been poked and prodded for many, many years, some parts have become very convoluted and ugly to maintain.
So I've tackled re-writing the main command parser to clean up this area. So far so good, it's been an interesting exercise as I re-discover all the little 'wrinkles' that were introduced over the years.
While this will probably not affect the user experience, it is a long overdue maintenance item.
George
|
|
|
Post by George on Feb 25, 2024 16:45:44 GMT -5
Robert: Without checking, Post_Do should just stack the commands on a FIFO basis.
|
|
|
Post by George on Feb 25, 2024 16:07:35 GMT -5
Robert: Thanks. I've installed and tried it out. It seems to handle the exiting Doc. well.
George
|
|
|
Post by George on Feb 25, 2024 14:35:52 GMT -5
Jo: The macro seems to run fine here (assuming I understand its purpose properly)
What does it do differently for REX files, I'm not sure about that part.
George
|
|
|
Post by George on Feb 25, 2024 13:40:30 GMT -5
Jo: How about:
Send me the macro. Try assigning the new primitive (CmdLog) to a key and invoking it, before testing. and sending me the log it creates (whether it crashes or not). The log is in the SPFLite Home Data folder.
George
|
|
|
Post by George on Feb 23, 2024 12:07:37 GMT -5
OK, that's the only reason I could come up with as well.
George
|
|
|
Post by George on Feb 23, 2024 10:52:58 GMT -5
Robert: I got notified of your post, but I can't access it; it says I'm 'not authorized' - ?? - but I'm an administrator, so ...
Does it look normal to you? Can you still access it?
George
|
|
|
Post by George on Feb 13, 2024 12:24:59 GMT -5
Robert: I did a quick check, the option for 'only one SPFLite' has been around for over 10 years, and multiple Instance support for almost 5 years. And we've never had so much as a comment (good or bad) from users about the 'problems' you want solved.
George
|
|
|
Post by George on Feb 12, 2024 16:18:53 GMT -5
My basic response is the same, when I hear a 'hue and cry' from the users that what we have is causing them problems, I will 'do something', until then, I still say this is a 'make work' project.
George
|
|
|
Post by George on Feb 12, 2024 14:46:00 GMT -5
Robert: It's not quite that simple. Multiple instances, regardless of the Options setting can always be created by using the OPEN/OPENE/OPENB/OPENV commands.
Users can also have unique Instances opened, so as well as versions, we also have Instance names and the Beta/non-Beta condition.
It all gets messy in the code, as well as the testing, and as I said, it has been like this for years and I don't hear a huge hue & cry from users to 'make this messy condition better'.
I'd like to hear from users (other than you) who feel this area needs addressing, because I just don't see the need. I'm sure 99.9% of users only ever have 1 version installed and running, in which case all this discussion is moot.
George
|
|
|
Post by George on Feb 11, 2024 14:06:42 GMT -5
OK then, other than turning OFF 'Only one SPFLite running', give me a solution for how I test new versions while having the production version 'up' doing useful work.
And that solution also has to let me test the 'Only one SPFLite running' logic.
Yes, I know, I could put in some arbitrary code to do this, which I would have to edit and set on and off as needed, a royal PITA.
Also "Broken?" And just how does what is done currently 'break' anything? Other than violating the exact legal phrasing of the Options ON/OFF text, it 'breaks' nothing, at most it is an annoyance. And I'm sorry, but Beta testers, by their nature, have volunteered to put up with some annoyances in order to help development.
This is simply a tempest in a teapot.
George
|
|
|
Post by George on Feb 10, 2024 14:08:19 GMT -5
Sorry Robert: No. Your suggestion is simply a make-work exercise. Besides, I prefer the "Beta" addition over another numeric level. It stands out, users probably have no interest/knowledge of a numbering system where the last digit means "Beta" if it's non-zero. Seeing "Beta" is as clear as day to anyone.
The current code has been like this for a very long time, running without incident. It only came to our attention after the change you requested to have "Beta" added to the title bar, and I slipped up and introduced an error.
If I hadn't missed a simple 1 line change in the test for unique instance, it would have continued along, just as before, without incident.
Also, I certainly don't want to go about changing version numbers during the day just because it's 'busy'. My #RESOURCE version Include file is created automatically for me overnight by a scheduled task which executes a small Basic program to update this file.
This Pgm would also need tweaking, yet more nuisance work.
Let's leave well enough alone.
George
|
|