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

License? #2

Open
robmcmullen opened this issue May 1, 2017 · 1 comment
Open

License? #2

robmcmullen opened this issue May 1, 2017 · 1 comment

Comments

@robmcmullen
Copy link
Contributor

I have modified your code to support the ][+ in addition to the //e (so a switch to select 6502 or 65C02).

Based on your reaction to my pull request to fix linux support (I am on python 2; see #1 (comment)) I'm not sure you'll be interested in the changes.

So if you're not interested, can I fork your code legally? I see your copyright which implies it's not open source, but it's on GitHub so... ? Would you mind adding a license file or letting me know if you'll allow it? I can always write my code from scratch but it's nice to start from a well-tested base as your code seems to be.

See you at that Atari convention in KC in a few months; I'm sure we're slowly converting everybody. And this is where you say Boo Atari.

@blondie7575
Copy link
Owner

I'm definitely interested in a PR for this. I stuck to 65c02 opcodes here because the generated code's size is the main challenge, and every byte counts. I also imagined that aux memory would come into play eventually, to help offset that pain. That said, there's still potential value here for a II+, so I'd like to see your PR.

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