From: Kendall B. <Ken...@sc...> - 2000-07-12 19:55:16
|
Hi All, Nelson mentioned in a prior email to this list about getting our SciTech changes merged into this new SourceForge project. It appears that this has now taken place, and I am in the process of syncing up to the newly merged sources and will be testing them with our projects. Thanks Nelson! Some other comments from what Nelson said earlier: > I`ve been trying to find people interested in working on Nasm and > so far I haven`t had much luck. Perhaps this is why the original > project died, nasm must seem very complete to most developers by > now. We actually also tried to revive the NASM project, and set up a mailing list for people interesting in using and enhancing NASM some time ago. Right now there are about 40 people subscribed to our mailing list, and I sent out an email to that list a few days ago telling them about this new project. I hope those people will also subscribe to this new mailing list, as I mentioned that we plan to close down our list so all traffic should end up here. > All that I would expect would be that if you make further > substantial changes to contribute them to the project and as the > number of active members grow we can all participate in keeping the > tree sane. If we do make changes to NASM I have everything set up with Perforce so that I can easily merge my new changes automatically back into the CVS respository. Hence I don't develop directly with CVS, but with a branch in Perforce. Due to the powerful branching stuff in Perforce (and some external programs I have written ;-), it makes it real easy to keep up to date with CVS projects and submit changes back. BTW, has anyone looked into integrating the NASM patches that AMD did to include better support for MMX and 3DNow stuff in NASM? I have the latest patches that they sent me on the SDK, but have not had a chance to look into it. If you want I can post the patches to this list so we can look into making sure those changes and updates are included in this new version. BTW2, perhaps we should change the version on this new NASM to '0.99'? BTW3, it would be preferrable if our TASM_COMPAT stuff is all compiled in by default. I did my best when I added the latest changes (which I submitted multiple times to the old developers, but they never got integrated) to ensure that regular NASM mode was not changed, and the TASM compatible mode is activated with the '-t' command line switch. Regards, +---------------------------------------------------------------+ | SciTech Software - Building Truly Plug'n'Play Software! | +---------------------------------------------------------------+ | Kendall Bennett | Email: Ken...@sc... | | Director of Engineering | Phone: (530) 894 8400 | | SciTech Software, Inc. | Fax : (530) 894 9069 | | 505 Wall Street | ftp : ftp.scitechsoft.com | | Chico, CA 95928, USA | www : http://www.scitechsoft.com | +---------------------------------------------------------------+ |