| Age | Commit message (Collapse) | Author |
|---|
|
Add bracket or space to some keyword completions
|
|
Fix subtracting colors and quats
|
|
|
|
Several edits to the GDScript docs
|
|
|
|
GDScript(2.0) Documentation generation system
|
|
GDScript default argument override bug fix
|
|
|
|
|
|
Fix VariantInternal initialization and setting of object
|
|
Implement proper error print, Fixes a crash when no error messages are generated by the analyser.
|
|
- Initialize Object pointer to nullptr so it's not used by mistake.
- When setting an Object check if it's a reference so refcounting works
as intended.
|
|
Values that are passed by reference are not suited for being constructed
at compile time because in this case they would be shared across all the
construction statements.
|
|
- ClassDoc added to GDScript and property reflection data were extracted
from parse tree
- GDScript comments are collected from tokenizer for documentation and
applied to the ClassDoc by the GDScript compiler
- private docs were excluded (name with underscore prefix and doesn't
have any doc comments)
- default values (of non exported vars), arguments are extraced from the
parser
- Integrated with GDScript 2.0 and new enums were added.
- merge conflicts fixed
|
|
Fix: #41766
|
|
generated by the analyser.
|
|
Fixes crash when parse_expression returns nullptr.
|
|
GDScript: range function type check bug fixed
|
|
Fix crash due to unreachable code in properties
|
|
Fix: #43586
|
|
This is not user accessible anymore so it does not need to be show in
documentation.
|
|
GDScript: Improve handling of operators
|
|
Some GDScript fixes
|
|
- Use the new functions in Variant to determine the validity and resulting
type of operators.
- Split the operator function in codegen between binary and unary, since
the unary ones have now a special requirement of having the second
argument to be the NIL type when requesting info.
|
|
It can wait until the analyzer itself is destructed, otherwise other
phases might be using freed parsers.
|
|
Otherwise this may lead to a crash when the dependency is not present.
|
|
|
|
A couple of GDScript fixes
|
|
It was mistakenly returning the source instead of the result.
|
|
The call of range() in a for loop is optimized to use int or vectors, to
avoid allocating an array, however the type was set as array still. With
the new typed VM this is an issue as the type mismatch the actual value,
resulting in wrong instructions to be selected.
|
|
- Replace the for loop temporaries by locals. They cause conflicts with
the stack when being popped, while locals are properly handled in the
scope.
- Change the interface for the codegen so the for loop list doesn't live
through the whole block if it's a temporary.
- Keep track of the actual amount of local variables in the stack. Using
the size of the map is misleading in cases where multiple locals have
the same name (which is allowed when there's no shadowing).
- Added a few debug checks for temporaries, to avoid them being wrongly
manipulated in the future. They should not live more than a line of
code.
- Rearrange some of compiler code to make sure the temporaries don't
live across blocks.
|
|
Only for built-in types.
|
|
|
|
Methods from builtin types can be called by using the function pointer
when the argument and base types are known at compile time.
|
|
|
|
When the base type is known at compile-time, we can get a direct
function pointer that is faster than the regular set/get paths.
|
|
It now uses the direct operator function pointer, which increases
performance in evaluation.
|
|
Almost all instructions need variant arguments. With this change they
are loaded in an array before each instruction call. This makes the
addressing code be localized to less places, improving compilation
overhead and binary size by a small margin.
This should not affect performance.
|
|
To improve organization and reduce the size of compilation units.
|
|
|
|
|
|
|
|
* Using C-style function pointers now, InternalMethod is gone.
* This ensures much better performance in typed code.
* Renamed builtin_funcs to utility_funcs, to avoid naming confusion
|
|
|
|
|
|
Clarify that code in `assert()` should avoid side effects
|
|
Change DocData comparators for MethodDoc and ArgumentDoc to get a better
ordering of constructors.
|
|
|
|
The underscore prefix was used to avoid the conflict between the `RID` class
name and the matching enum value in `Variant::Type`.
This can be fixed differently by prefixing uses of the `RID` class in `Variant`
with the scope resolution operator, as done already for `AABB`.
|
|
|