ASM Community

I sometimes still add commandline args to my win32 apps so thanks, I'll probably use this at some point :)
Sure beats reinventing the wheel or copy-pasting code across projects as I often do for this kind of thing.

I prefer more "professional" command line parsers (for instance LINK.EXE)
with keys as a /Fn: c:\Myprogs\Myfilename.asm
and without quotes, double quotes, etc...(why to write more?!..)
I coded similar in my program Bin2Obj.zip:
http://www.asmcommunity.net/board/attachment.php?postid=118516

Regards,
Lingo

didn't f0dder make bin2o?

Well, I only convert once to obj... so speed is not factor. Size was never factor for me. But that's just me :)

I don't see how your tool automatically becomes faster and smaller because it was coded in assembly?
Such assumptions usually lead to 'tools' that are inherently bad designed and slow. The size is also usually non-optimal.
Not to say anything about your Bin2Obj tool...

true, true. I stopped working on bin2o when it met my requirements, anyway. There's a lot of room for improvement, like accepting textfile list instead of cmdline arguments, adding a symbol with the size of the data, etc. But who cares, it works fine ^_^

comrade,

". so speed is not factor. Size was never factor for me. "

I'm wondering what your assembly life without factors is, hence you are not a factor too because of that...

"but not much argument today"

The arguments are in my shared source code



death,

"I don't see how your tool automatically becomes faster and smaller because it was coded in assembly?"

I assume you are blind for assembly C++ moron (as f0dder) because:

"it was coded in assembly BY ME"
and I shared my source code...
and if you can read assembly....
and if you red and understood the A. Fog's book...
and if you can use his methodology like me...

Ooops, you can see how I use A. Fog's methodology here:
http://www.asmcommunity.net/board/showthread.php?threadid=4358&perpage=15&pagenumber=2


"Such assumptions usually lead to 'tools' that are inherently bad designed and slow.
The size is also usually non-optimal."

What is this? Emotional and powerless HLL blab, blah, bla..
Where is your "faster" and "optimal" assembly code?
Don't forget you are just a blind moron


Not to say anything about your Bin2Obj tool.."

I'm not wondering why...he, he


Regards,
Lingo

be nice people :)

lingo you would need quotes for "files with spaces in or the occassional weird char?.no"

Well, that's not true. It's been a while since I wrote anything that needed optimization, though. And even when I write 'intensive' stuff, I prototype it in C, play with different algorithms, etc - then I decide whether or not to write assembly implementations.

Also, I'm not going to claim I'm a better asm optimizer than you are, that would be silly. I can get my stuff running decently at my target platforms, this is what matters to me. I'd rather focus on program design, security issues, extendability than writing the fastest possible wndproc handler :)

hutch, masm by default wants names prefixed with underscores - so use /id:_mytest on the bin2obj commandline and you'll be fine. Otherwise, figure out how to make masm generate non-underscore-prefixed EXTRN references for data (perhaps by defining the data as a proc with syscall calling convention, heh)