Re: HLA Lib

http://webster.cs.ucr.edu/AsmTools/HLA/stdlib2/index.html
allright, so my few points:

1. why does integer reading routines skip over "," ":" and ";"? I
understand skipping over blank chars in typed input, but these are IMO
not a good idea. Same for underscores in fileio.geti funcs. Can you
explain why you decided so?

2. I think you should also provide some routine to read stdin even
without skipping initial blank characters. Most of times it is fine,
but sometimes people may not want this.

3. reported bug with bad error catching of errors returned by linux
remained there. "os_fileio/readln" for linux is screwed copypastery of
win version ;) :DDD

4. have you been thinking about speed of your routines a little bit? I
know it isn't the most important stuff, but still some border is
required. I believe that calling all the APIs in fileio.eof for every
converted char of fileio.geti is little too much

5. stdin input deserves same kind of attention as file I/O. There are
several things taken in account for file I/O, but not handled in stdin
I/O. Remember stdin can be any type of file handle aswell. Handling of
EOF is a good example.

.

Relevant Pages

  • Re: Trying to toss input with non-printable characters
    ... > I'm trying to write a tiny script that reads its stdin and, ... > the input line has above a particular threshold of characters ... # Drop lines containing too many bad chars in a row ...
    (comp.lang.tcl)
  • Re: getline - sort of
    ... I need to read a string from stdin which I will then process as digits ... with sscanf. ... I also need to detect when more or fewer chars ...
    (comp.lang.c)
  • Re: File I/O using NASM in 32-bit mode
    ... and my buf in stdin is 4 chars ... when i start a new programs seems its stdin has "aaaaaaaaaaa" ... WriteFile(in, buf, len, &var, 0); ...
    (alt.lang.asm)
  • Re: File I/O using NASM in 32-bit mode
    ... when in windows 95 if i write in stdin ... and my buf in stdin is 4 chars ... WriteFile(in, buf, len, &var, 0); ...
    (alt.lang.asm)