Use a binary search for resolving #defines

BYOND Forums

Announcements · BYOND Help · Bug Reports · Feature Requests · Beta Testers · Beta Bugs · Developer Help · Design Philosophy · Demos & Libraries · Tutorials & Snippets · Art & Sound · Classified Ads · Game Updates · Contests & Events · Linux Talk · On Topic · Off Topic

ID:2357542

Mar 30 2018, 3:12 am

MrStonedOne

Resolved

The parser tried to match words to #define macros using a linear search of all macros, which could be slow for large projects. Macros are now handled via a binary search.

Applies to:

Dream Maker

Status:

Resolved (512.1418)

This issue has been resolved.

Resolving defines uses a linear search, this could be made a binary search or other logarithmic solution to speed up compile time.

Mar 30 2018, 1:04 pm
Lummox JR	Lummox JR resolved issue with message: The parser tried to match words to #define macros using a linear search of all macros, which could be slow for large projects. Macros are now handled via a binary search.

Mar 31 2018, 8:27 am
MrStonedOne	So on /tg/ on 1418 we encountered a bug where something that was defined twice (accidentally) started resolving to the formal value rather then the latter value. Likely not intended behavior.