I didn't see any other responses to this, so let me say what I can. I can't
help with anything specific to nasm, but as to scanf ... did you consult
its man page?
A quick read of it confirms that %n is, at best, unpredictable in how it
will be interpreted (or perhaps "at worst", since I think "
Supose I write a program in nasm that does this:
Enter a set of integers separated by spaces:
22 31 456 87
Suppose that in the module I am calling scanf to repeatedly parse the
ints from stdin to place in an array, each index of which is 32 bits in
size to hold a 32 bit unsigned int.
I've been
Comments inline.
At 11:58 PM 11/18/02 +1300, cr wrote:
Sorry for the long delay. Real Life (TM) interfered with my investigations,
and also a point you mentioned brought up a possible complication which I'll
mention at the end...
Perfectly understandable. I hope you will be equally understand
> - Original Message -
> From: "Adam Luchjenbroers" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, November 15, 2002 9:05 PM
> Subject: Passing the entire command line
>
> > While bash can retrieve the different commandline values using the
>
> variables
>
> > $1, $2, $3, etc
Put them between ""
- Original Message -
From: "Adam Luchjenbroers" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 15, 2002 9:05 PM
Subject: Passing the entire command line
>
> While bash can retrieve the different commandline values using the
variables
> $1, $2, $3,
I don't know of a way to make it put the machine name at the beginning
of each line.
As a partial solution, you could put the machine name into the log file
before the copy:
echo ${machinename} >> $log
cp --preserve . and so on.
I tend to put a lot of date stamps in log files as well as
Sorry for the long delay. Real Life (TM) interfered with my investigations,
and also a point you mentioned brought up a possible complication which I'll
mention at the end...
On Friday 01 November 2002 05:05, Ray Olszewski wrote:
> At 02:29 AM 11/1/02 +1300, cr wrote:
> >[...]
> >
> >I don't h
