adding function start and end line number #219
Merged
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.
This pull request introduces improvements to function introspection in the
phper
library and updates documentation to reflect a more accurate parameter type. The most important changes are the addition of new methods for retrieving a function's declaration line numbers, a clarification in a documentation example, and a minor renaming for clarity.Function Introspection Enhancements:
get_line_start
andget_line_end
methods to theZFunc
struct inphper/src/functions.rs
, allowing retrieval of the start and end line numbers for user-defined and evaluated functions.Documentation Update:
phper-doc/doc/_06_module/_02_register_functions/index.md
to show the parameter type as?\MyNamespace\MyInterface
instead of?class_name
, reflecting the actual interface type used.Codebase Consistency:
get_lineno
toget_opline_lineno
in theExecuteData
struct inphper/src/values.rs
for improved clarity regarding its purpose.