Index
> Main > flat assembler 1.53 |
| Author |
|
|
Tomasz Grysztar
The official release of fasm 1.53 is now available in the Download section.
There are no new features added that were not present in 1.52 version - this is mainly a bug-fix release. Last edited by Tomasz Grysztar on 30 Jul 2004, 16:05; edited 1 time in total |
|||
23 Jun 2004, 15:33 |
|
|
Tommy
Seems good!
What about an online version of the "To-Do" and "What's new" list? |
|||
|
24 Jun 2004, 08:17 |
|
|
vid
good idea
|
|||
|
24 Jun 2004, 10:52 |
|
|
Jaques
i would be helpful
|
|||
|
24 Jun 2004, 15:03 |
|
|
Rookie
That's because Windoze uses Carriage Return-Line Feed (0Dh,0Ah) to designate a new line (that is 2 bytes), while Linux uses just the LF (0Ah) (just one byte). And as asm has a lot of short lines (which leads to a lot of new line sequences), 1+1+1+... leads to 18,302-17,298 bytes difference between the two files.
_________________ This is who I choose to be. |
|||
|
25 Jun 2004, 20:34 |
|
|
comrade
if that is the case, parser.inc should have 1004 lines
|
|||
|
26 Jun 2004, 02:20 |
|
|
jekyll
1005 lines
|
|||
|
26 Jun 2004, 03:09 |
|
|
Quant
Ok, I understand, thanks for your descriptions...
_________________ Regards... |
|||
|
26 Jun 2004, 08:26 |
|
|
scientica
Just for the fun of it (and to learn how to make patches), I made a patch for 1.52 to 1.53 (linux version).
I created the patch like this: Code: diff --unified --recursive --new-file fasm-1.52/* fasm-1.53/ > patch-fasm-1.53 To apply the patch do this: Code: cd your/fasm-old-verion/dir cat path/to/patch-fasm-1.53 | patch -p1 # now you'll need to recompile fasm, as it's not pached fasm source/Linux/fasm.asm fasm #now just copy the file to the "bin-dir" where you got the fasm binary, or update the symlink I'm gonna try to patch the libc version of fasm, I think it'll be a smooth update 
btw, the code base for Linux is 18 565 lines (cat *.inc Linux/* | wc -l), Win32 is 18 738 (cat *.inc Win32/* | wc -l) and the DOS is 19 310 (cat *.inc DOS/* | wc -l). 
(with out comment lines and empty lines: 18 387 for Linux (cat *.inc Linux/* | grep -E ^\[^\;\] | grep -E ^\[^\n\] | wc -l) 18 549 for Win32 (cat *.inc Win32/* | grep -E ^\[^\;\] | grep -E ^\[^\n\] | wc -l) 19 084 for DOS (cat *.inc DOS/* | grep -E ^\[^\;\] | grep -E ^\[^\n\] | wc -l) ) btw, parser.inc has 1004 lines (cat parser.inc | wc -l) [edit]It seems it's fine to patch the libc version, however, you'll need to remove afew lines from the patch-fasm-1.53.asm patch, as it contains all files, not just the source files (which is the only files that comes with the libc version). I'm attaching the patch for the libc verison. appl the libc patch like this: Code: cd somedir tar xzvf fasmlibc.tgz cat /path/to/patch-fasm-1.53_libc_src | patch -p1 cd source/libc/ fasm fasm.asm fasm.o gcc fasm.o -o fasm strip fasm # (optional) [/edit]
_________________ ... a professor saying: "use this proprietary software to learn computer science" is the same as English professor handing you a copy of Shakespeare and saying: "use this book to learn Shakespeare without opening the book itself. - Bradley Kuhn |
|||||||||||||||||||||
|
28 Jun 2004, 18:29 |
|
|
crc
Quote: I'm gonna try to patch the libc version of fasm, I think it'll be a smooth update I'm almost done some updates to the libc version . Once complete (probably tomorrow), it'll return the actual error code, rather than "0" after each run. Since I'm doing this mainly for the BeOS port, so it'll be posted to the forum there. |
|||
|
29 Jun 2004, 01:09 |
|
|
scientica
Will you make a patch? (I've begun to like patches
They're small, neat&cute )
I think you should be able to apply the libc patch with out problems (as it only conaints the cnages in the cross platform code. btw, it would be nice to see fasm with a CVS, and some neat CVS viewer like"FreeBSD-CVSweb". |
|||
|
29 Jun 2004, 21:56 |
|
|
fasm9
gnu arch?
http://www.gnu.org/directory/arch.html |
|||
|
29 Jun 2004, 22:04 |
|
|
crc
Yes, I will provide a patch as soon as I finish testing it
CVS isn't essential for smaller projects like FASM. I tried the CVS route with RetroForth, and it was actually more painful than managing the codebase by hand! Recently I *did* write a simple version control system that runs under Linux & BeOS though. (I'll release it after I add support for generating+applying patches in it) |
|||
|
29 Jun 2004, 22:08 |
|
|
scientica
Well, once one gets used to CVS it rocks
Cervisia is quite nice for viewing/handling cvs dirs. I might not use CVS as intended, it's sort of a backup/screw up tracker  I use it to keep track of what beating I've done to the poor sources. |
|||
|
29 Jun 2004, 22:21 |
|
|
crc
My VCS provides simple versioning (per checkin), backups, producing release binaries, cleaning up temporary files, generation of diff's, and handling multiple projects easily. It's a BASH shell script (uses tar, gzip, cat, bash, retroforth, sed, diff, & patch). CVS (and most other VCS systems) are intended for multiple developers working on a single codebase. Small projects seldom have this, and all changes have to go through a common source (the project maintainer) anyway. I used CVS on and off for over three years before giving up on it. Sometimes simpler solutions are better
|
|||
|
29 Jun 2004, 22:29 |
|
< Last Thread | Next Thread > |
Forum Rules:
|