This document contains internal notes and information for rmToo developers.
The project maintains internal tracking numbers for exceptions and error codes. The current status is tracked in development files for consistency across the codebase.
Current Status: Next free exception number: 118
This helps ensure that error codes and exception identifiers don't conflict across different parts of the system.
- Exception numbers are assigned sequentially
- Developers should use the next available number when creating new exceptions
- Update the tracking file when assigning new numbers
- Document exception purposes for future reference
- Maintain consistency in error handling
- Use standard exception types where appropriate
- Follow Python exception handling best practices
- Include meaningful error messages
The project includes various internal files for development tracking:
- Exception number tracking
- Development notes
- Internal documentation
- Build system helpers
- Keep internal tracking files up to date
- Review and clean up obsolete tracking information
- Maintain consistency across development team
- Document significant changes
- Check the current next available number
- Use the next sequential number for your exception
- Update the tracking file with the new next number
- Document the exception purpose
- Follow project coding standards
- Use meaningful exception names
- Include helpful error messages
- Follow the established numbering system
- Update documentation as needed
- Contributing Guide - How to contribute to rmToo
- Development Guide - Setting up development environment