-
Notifications
You must be signed in to change notification settings - Fork 147
Remove the hard limit due to EATTENSOR #490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
I don't follow this. Why does EATTENSOR need "passing in" at all? The define is active inside these functions of course. Shouldn't f5c061e#diff-dfad395d67eb6654e019817a74f727d798e04807b660529206715a8f3b141503R1565 just be |
|
There exist calls of |
|
OK I see, I misinterpreted it as some kind of limit on the number of arguments that can be in the pattern. |
The EATTENSOR flag is now passed to CheckWild()/AddWild() via "type" instead of "newnumber". Fixes form-dev#268.
|
Added 2 tests for #268. |
|
This one has caused a regression actually, here is an example which is the first thing This terminates with |
|
Good catch, thanks! A somewhat minimized example that gives Vargrind errors is: |
|
I really don't understand why I overlooked this line. Definitely, we need more tests... |
Try to fix #268.
I'm still not sure why
EATTENSORis called so (maybe there was a certain reason 21 years ago).