Code generation for wxPerl and wxRust #1556
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This version uses wxWidgets 3.2.
This affects the Event Handler dialog. PHP had already been replaced with a Rust tab, but the variable names had not been changed.
Similar to the other languages, this adds unimplemented events as comments in the source code. Closes #1530
This was still the old PHP lexer that we no longer use.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The primary focus of this PR is to start generating code in support of the new wxPerl 3.005 which supports wxWidgets 3.2. The secondary focus was to start generating code for wxRust, based off the wxRust2 implementation. The Rust code is neither tested nor compilable -- it's just to get the underlying code generation for Rust in place while work on wxPerl is being done.
The work on event code generation for wxPerl also includes adding unimplimented C++ events for forms that aren't using a derived class, which closes #1530. These events are in a comment block at the end of the forms class definition so that they can be copied and pasted to the user-editable section as needed.