GithubHelp home page GithubHelp logo

Comments (15)

FraGag avatar FraGag commented on August 27, 2024 2

@Clownacy I changed it.

Should we also rename the master branch to something else, like asm68k, for clarity?

from s1disasm.

Awuwunya avatar Awuwunya commented on August 27, 2024 1

Then we come to the whole debate about AS vs ASM68K ultimately. You can't win in the argument because both have some serious flaws. Until we have a better solution (eg someone creates a competent assembler), switching to AS branch as default would be a sensible alternative, provided Flamewing's fixed version of AS is implemented and improved upon, and tutorials are updated to reflect the change.

from s1disasm.

FraGag avatar FraGag commented on August 27, 2024 1

Also, I just pushed a noop merge to the asm68k branch (from the AS branch) so that changes committed to the AS branch can be merged "more easily" to the asm68k branch. We should no longer merge the asm68k branch into the AS branch.

from s1disasm.

Brainulator9 avatar Brainulator9 commented on August 27, 2024

At the same time, if you know what you're doing, much of the code you mentioned can be migrated to ASM68K with little issue (at least SMPS2ASM and the Ultra DMA queue can be).

I actually find the ASM68K version easier to use, since you don't have to worry about recompiling tools with some program if you want to make larger modifications. Maybe this is just me being a noob, though.

EDIT: It took all day, but I managed to port Flamewing's SMPS2ASM back into something that ASM68K can use, maintaining all features yet still assembling bit-perfect Sonic 1 ROMs.

from s1disasm.

kramlat avatar kramlat commented on August 27, 2024

the entire point of using ASW is to not even have to do that. I am fine with that, as long as the asm68k branch just becomes a lesser branch that others can still use if they really want it.

from s1disasm.

MainMemory avatar MainMemory commented on August 27, 2024

I would say something about how many people hate AS, but I don't think any of them use this disassembly anyway so I guess it really doesn't matter.

from s1disasm.

Clownacy avatar Clownacy commented on August 27, 2024

...I was going to make the change today, but I realised that I don't have the permissions to change the repo's default branch.

@MainMemory, could you do it?

from s1disasm.

Clownacy avatar Clownacy commented on August 27, 2024

Yes, I think that's a good idea. Thanks.

from s1disasm.

Clownacy avatar Clownacy commented on August 27, 2024

Whoops, maybe I should leave this open until the MapMacros and Project Sonic 1: Two Eight branches are rebased on the AS branch.

from s1disasm.

kramlat avatar kramlat commented on August 27, 2024

I will take down all branches except one of my fork once this completes because they will officially be redundant

from s1disasm.

Brainulator9 avatar Brainulator9 commented on August 27, 2024

Perhaps the MapMacros and Project 128 branches should be split into ASM68K and AS versions?

from s1disasm.

kramlat avatar kramlat commented on August 27, 2024

Perhaps the MapMacros and Project 128 branches should be split into ASM68K and AS versions?

that would be a perfect idea, and for Sonic 1: twenty eight as well?

from s1disasm.

Clownacy avatar Clownacy commented on August 27, 2024

The problem with that is maintenance burden: it's bad enough that I have to keep 4 branches in sync with each other, so I'd really rather not bump that up to 6.

from s1disasm.

Brainulator9 avatar Brainulator9 commented on August 27, 2024

Project 128 is Project Sonic 1: Two Eight; I messed up the name.

Having 6 branches doesn't seem much worse to me, though, than s2disasm's 5 branches (master, megaplay, knuckles, classics, MapMacros). Then again, it's not like I've been able to handle much of the commit history here.

from s1disasm.

kramlat avatar kramlat commented on August 27, 2024

or we can bump it up to 8 if you prefer by adding a megaplay branch in each of the assemblers, or we can drop it to just 4: our as based branches and asm68k branch and if one wants something else,l they just fork it. the forks should still be accessible from the main repository and the one that wants an up to date asm68k sonic 1 with knuckles one, they could just fork the asm68k repository and pull changes into it over time. i.e. if they want 6 branches, they could just do what I was doing over these years, and they could simply just name their fork for an example, s1sidasm-asm68k-mapmacros-with-tails.

from s1disasm.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.