4 replies to this topic

[SmileyDude]

Has there been any thought into putting dasm up on github instead of sourceforge? I have a couple of things I was thinking of doing with dasm (fix 64-bit Intel OS X builds, Apple II header files, enhanced ERR pseudo-op) and having worked with github before, I thought it might be a nice home for it. It might spur some experimentation with it.

Is Andrew Davies still the maintainer for dasm these days? If not, who is?

Edited by SmileyDude, Tue Sep 27, 2011 8:01 AM.

[SmileyDude]

No responses here -- does that mean there isn't much interest or that this is wrong place or something else all together?

Thinking about it on my end, I'm going to go ahead and setup a github repo for the stuff I do with dasm. I'd much prefer that at least those changes should be available for others to benefit from. And github is easy to work with. If someone wants to be the owner of the "authoritative" repo on github, I'm fine with that -- we can just work out the details when we get to that point later. Since the code is under the GPL, anyone is free to take the changes I make anyway, so it's not a big deal.

I'll post up a link once I have it setup with some of my changes in place.

[SeaGtGruff]

SmileyDude, on Tue Sep 27, 2011 7:58 AM, said:

Is Andrew Davies still the maintainer for dasm these days? If not, who is?

I think Peter Froehlich is the current maintainer.

[Andrew Davie]

SmileyDude, on Tue Sep 27, 2011 7:58 AM, said:

Has there been any thought into putting dasm up on github instead of sourceforge? I have a couple of things I was thinking of doing with dasm (fix 64-bit Intel OS X builds, Apple II header files, enhanced ERR pseudo-op) and having worked with github before, I thought it might be a nice home for it. It might spur some experimentation with it.

Is Andrew Davies still the maintainer for dasm these days? If not, who is?

No "s", ta.

It's a bit of a mess. Peter took over the project and made a whole bunch of changes. Unfortunately, although he did remove some significant bugs that I'd introduced over the years, he also introduced a few new bugs which are pretty much show-stoppers for me. Macros, for example, are broken and don't always work reliably. So, DASM once again needs a revamp. I haven't heard from Peter for years and have no idea if he's still maintaining it. I don't have time to manage it, and I don't particularly care if it lives on Sourceforge or elsewhere. It's just a shame that it's now in a broken state and there are versions all over the place.
Time for a complete rewrite, IMHO.

[SmileyDude]

Hi Andrew --

Thanks for replying -- and sorry about the "s". I realized it too late to edit the post.

I would definitely like to know more about the showstopper bugs that you (and anyone else for that matter) are encountering. My own simplistic use of macros hasn't triggered anything bad yet, but that really doesn't mean much. I've seen other people refer to the macros as broken as well, so there must be something to it.

I did go ahead and put up a github repo if anyone is interested. It's at https://github.com/munsie/dasm . Feel free to use it. It's based on the last version of Peter's that I could find. I managed to fix the problem with the 64-bit Intel build on OS X as well and made dasm play a little nicer with Makefiles under Unix.

I don't want to say that I'm up to the task of maintaining dasm, but I'm certainly willing to give it some attention here and there. I will definitely take a look at any pull requests that I get, and as long as they don't generally make things worse, merge them into my repo.