|
|
Post by Stefan on Oct 14, 2022 6:15:02 GMT -5
FWIW, my 2 cents worth (and you're being overcharged!)
I can't get my head around KEEP and DROP at all. I can't help thinking that this command pair is a solution waiting for a problem.
And even then, by the time I've tagged all the relevant lines correctly so that KEEP and DROP might assist me, I could probably have completed the process by hand anyway.
|
|
|
|
Post by George on Oct 14, 2022 12:00:43 GMT -5
OK, way back when the universal search routine criteria data was re-organized, this error crept in. It was one of those boolean compound tests that worked before the change, but became illogical after the change.
DROP and KEEP have been corrected now.
But it does show that they have lain unused for years. I can see their usefulness, but 'unused for years' is worrisome. Should they be retired? They will now work (again), so it costs nothing to keep them.
George
|
|
|
|
Post by George on Oct 14, 2022 14:06:02 GMT -5
Hey Robert! No jettisoning at all. Without your ideas SPFLite would be a pale shadow of what it is. But yes, it's probably time for DROP/KEEP to retire.
George
|
|
|
|
Post by George on Oct 18, 2022 9:41:36 GMT -5
I am going to 'retire' DROP and KEEP.
George
|
|
|
|
Post by George on Oct 18, 2022 12:11:04 GMT -5
Sorry, yanking is so quick and easy, they're gone.
George
|
|
|
|
Post by George on Oct 18, 2022 12:35:00 GMT -5
Why, if it hasn't been used in years, and we're going to deprecate it, who can it impact?
George
|
|
|
|
Post by George on Oct 18, 2022 13:25:56 GMT -5
OK, how be I restore the code. The Doc has had it removed, so it will be simply be 'not mentioned' anywhere.
The code can go away later, the doc is harder to back out since I made many other changes in there at the same time, don't want to have to re-do them.
George
|
|
