[Nasm-bugs] [Bug 3392374] New: Request for new user account 'mateusz at viste.fr' submitted

[no-reply at bugzilla-nasm.gorcunov.org]

https://bugzilla.nasm.us/show_bug.cgi?id=3392374

            Bug ID: 3392374
           Summary: Request for new user account 'mateusz at viste.fr'
                    submitted
           Product: NASM
           Version: 2.12.xx
          Hardware: PC
                OS: Other
            Status: OPEN
          Severity: annoyance
          Priority: Medium
         Component: Assembler
          Assignee: nobody at nasm.us
          Reporter: mateusz at nospam.viste.fr
                CC: gorcunov at gmail.com, hpa at zytor.com, nasm-bugs at nasm.us

NASM is confused by its argument list when called with %1 %2 %3 parameters

On my FreeDOS system I use 'link' files in my %PATH% to call out the variety of
utilities I store on the disk. For nasm, the 'link' batch file looks like this:

  @ECHO OFF
  C:\DEVEL\NASM\NASM.EXE %1 %2 %3 %4 %5 %6 %7 %8 %9

This works with most utilities, but somehow nasm is confused about it. Example:

(of course the "nasm" command here refers to my 'link' batch, not to the nasm
executable directly)

Tested with nasm v2.12.02.

Also, out of sheer curiosity, I did a short test program with open-watcom just
to make sure that arguments are passed right, and it all seems good:

  #include <stdio.h>
  int main(int argc, char **argv) {
    int i;
    printf("got %d params:\n", argc);
    for (i = 0; i < argc; i++) printf(" %d='%s'\n", i, argv[i]);
    return(0);
  }

output, when called from within a batch file with all %1 %2 ... %9 parameters:

C:\>test a b c
got 4 params:
 0='C:\TEMP\T.EXE'
 1='a'
 2='b'
 3='c'

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are watching all bug changes.