parameterize irtree generation path with identifier resolution rules; in most cases, we want the usual order: implicit accesses -> locals -> registers -> globals/tlocals/types/procedures -> macros; but if we are specifically evaluating a call expression tree, we want to prefer callables - in this case, macros should be prioritized.

Browse Source

...

This commit is contained in:

Ryan Fleury

2025-05-12 11:56:57 -07:00

parent 8688322a43

commit fe3cac7ac3

8 changed files with 863 additions and 753 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

src/eval/eval_ir.c

+457 -426

File diff suppressed because it is too large Load Diff