Larry Campbell
Larry Campbell
The following patch fixes this bug (and doesn't cause any of the existing NSPredicate tests to fail), but I suspect it may just be a bandaid for a specific case...
Yes, the following patch does seem more general, fixes my use case, and doesn't break the existing NSPredicate tests: ``` --- NSPredicate.m.orig 2022-01-30 10:27:07.177865334 -0500 +++ NSPredicate.m 2022-01-30 10:36:17.211753217 -0500...
This patch fixes these bugs: ``` --- NSPredicate.m.orig 2022-02-09 20:44:25.987056355 +0000 +++ NSPredicate.m 2022-02-10 16:54:05.270872389 +0000 @@ -2535,17 +2535,17 @@ if ([self scanPredicateKeyword: @"FIRST"]) { left = [NSExpression expressionForFunction: @"_first"...
Your fix looks plausible. Unfortunately it's a very rare occurrence, and our release process makes it harder to take a new version of gnustep-base quickly than it does to take...
Thanks. I'm building with clang/llvm, and with these configure options for gnustep-make: --enable-objc-nonfragile-abi=yes --enable-native-objc-exceptions=yes --with-library-combo=ng-gnu-gnu which I think means I'm using the new ABI. I will try to shrink the...