Re: FIRST new bug?!?! =)

> how on earth did you remember to make a 255/256 char long filename ?
> Is that the situation when your program doesn't check if your filename is
> longer than 255 chars supported by OS and you badly need that 256.th
> character ?

Not really that important. I was just trying to figure out how long of
a name somebody could use for thier jobfile. I noticed after a certain
point it froze. Simple fix, just test the length of the string before
storing. Spaces seem to work in names as well. To bad the filer
doesn't sow long names yet though.

TW

.

Relevant Pages

  • [PATCH] Make do_execve() take a const filename pointer
    ... Make do_execvetake a const filename pointer so that kernel_execvecompiles ... asmlinkage int ... /* sys_execveexecutes a new program. ... char * filename; ...
    (Linux-Kernel)
  • [PATCH] Make do_execve() take a const filename pointer
    ... Make do_execvetake a const filename pointer so that kernel_execvecompiles ... asmlinkage int ... /* sys_execveexecutes a new program. ... char * filename; ...
    (Linux-Kernel)
  • Re: Which programming method is better?
    ... process("standard input", stdin, flags) ... and not a filename argument. ... preincrement argv first. ... I'd also go with const char* instead of char*, ...
    (comp.lang.c)
  • Re: case insentisive file search
    ... CopyStringPrefix(const char *String, size_t PrefixLength) ... FileName = CopyString; ...
    (comp.lang.c)
  • Re: FIRST new bug?!?! =)
    ... how on earth did you remember to make a 255/256 char long filename? ... Is that the situation when your program doesn't check if your filename is ... > STO ...
    (comp.sys.hp48)