Implement register unexposed classes #951
Closed
Conversation
This file contains hidden or 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
Daylily-Zeleen
force-pushed
the
daylily-zeleen/register_class_without_exopsing
branch
from
1d267e9 to
1e4b5b3
Compare
akien-mga
added
the
enhancement
Daylily-Zeleen
force-pushed
the
daylily-zeleen/register_class_without_exopsing
branch
from
1e4b5b3 to
f74c472
Compare
|
Replace by #970. |
Daylily-Zeleen
deleted the
daylily-zeleen/register_class_without_exopsing
branch
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.
Need #69653.
It seems that register methods are quite redundant.
I add
register_virtual_class()andregister_internal_class()just likeregister_abstract_class()( for making style consistent).Now, we can develop a GDExtension plugin just expose core function classes without tool classes.