-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No standard function header format #1
Comments
Suggestion: ;FUNCTION compiler calling_convention name entry_label parameter_count any additional comments Example: ;FUNCTION dcpuc registercall itoa itoa_FUNCTION 2 |
@Blecki: Should it be |
This isn't for indicating a dependency, this is so that tools (for example, a compiler) can find the function and call it properly. |
Just realized you might be confusing 'function header' with a 'header file', such as C uses. To clarify, separate concepts. This is for meta data attached to the function that compilers would use to properly call the function. This is not about importing one source file into another. |
@Blecki: |
Oh, Alright. All that's important is that it include all the information, and start with ; so assemblers interpret it as a comment. So how about |
No description provided.
The text was updated successfully, but these errors were encountered: