It's not clear where all error messages and debug strings are located. Many of them are directly contained within the functions themselves, and some are not in expected locations or of expected types (i.e. type errors are typed, but runtime errors are not typed always). This may be a significant issue for future engineers/researchers looking to work on or adjust aspects of BoGL to better serve as a teaching language.
A possible solution would be put together a 'Strings' or 'ErrorMessages' module that could be used to factor all these out. This would make it easy to point future researchers where they need to look for any error/debug messages that show up, and also makes it easy to adjust string responses without having to dig through or having to understand the core codebase.
It's not clear where all error messages and debug strings are located. Many of them are directly contained within the functions themselves, and some are not in expected locations or of expected types (i.e. type errors are typed, but runtime errors are not typed always). This may be a significant issue for future engineers/researchers looking to work on or adjust aspects of BoGL to better serve as a teaching language.
A possible solution would be put together a 'Strings' or 'ErrorMessages' module that could be used to factor all these out. This would make it easy to point future researchers where they need to look for any error/debug messages that show up, and also makes it easy to adjust string responses without having to dig through or having to understand the core codebase.