Skip to content

Parse and generate code for function parameters #9

Open

Description

@anachrocomputer

It's only a list of <expression>s, how hard can it be? But we'll also need to implement pushing them onto the stack and popping the stack after the function returns.

Activity

  1. anachrocomputer commented on Jul 2, 2026

    @anachrocomputer
    OwnerAuthor

    How hard can it be? Quite hard, because a) the stack frame is 2 bytes bigger if there's a 'register' variable and b) parameters must be evaluated and pushed onto the stack in reverse order so that 'printf()' can be implemented. See 'test/functions/arity_var.c'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions