Skip to content
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

Allow configuring sections #4

Open
ISSOtm opened this issue Jan 14, 2024 · 2 comments
Open

Allow configuring sections #4

ISSOtm opened this issue Jan 14, 2024 · 2 comments
Milestone

Comments

@ISSOtm
Copy link
Contributor

ISSOtm commented Jan 14, 2024

Currently, each script is emitted as an individual ROMX section.

  • One may want to emit scripts to ROM0, for example (and, if RGBDS later allows arbitrary section kinds via hardware description files, others);
  • One may want all scripts to lie within a single section.

I think this could be solved via a CLI switch; in particular, if the section type given is empty, no section directives would be emitted.

@evie-calico
Copy link
Owner

In my original drafts of the language (and maybe the c++ version?), this was determined by the env; i must have just forgotten it.

That being said, i don't think a command line flag is the right option. I think the best way to do it would be to define a default per env, with overrides for individual scripts. The only issue is that i don't have any ideas for the latter's syntax.

@ISSOtm
Copy link
Contributor Author

ISSOtm commented Jan 16, 2024

Perhaps mimicking the pool = syntax? I'd implement it by making the LHS into a regular ident instead of piling on keywords, since those'd quickly clog up the available names for variables and functions.

@evie-calico evie-calico added this to the v1.0 milestone Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants