Path: utzoo!utgpu!watmath!clyde!att!osu-cis!dsacg1!dsacg2!nor1675
From: nor1675@dsacg2.UUCP (Michael Figg)
Newsgroups: comp.sys.amiga
Subject: Re: Examine and ExNext return codes
Summary: Blame it om while.
Keywords: ints, Examine
Message-ID: <247@dsacg2.UUCP>
Date: 29 Dec 88 13:35:31 GMT
References: <246@dsacg2.UUCP>
Organization: Defense Logistics Agency Systems Automation Center, Columbus, OH
Lines: 34

In article <246@dsacg2.UUCP>, nor1675@dsacg2.UUCP (Michael Figg) writes:
> .
>   while((success = ExNext(lock,fib)) != 0);
>   {
>     printf("Success equals %d\n", success);
>     printf("File name: %s\n",&fib->fib_FileName[0]);
>   }
>   printf("Success equals %d\n",success);
> }
> .
> Okay, I just noticed the ";" after the while statement which expains alot
> but just changes the scope of the question to why am I getting zero? Also
> in the first printf Rob uses a "%ls" which I have never seen before. In the



After I spent more than 5 seconds staring at this I realize that the output 
is probably what is expected since the while is probably going through all
the entries until it hits the end, then it prints the last entry and the zero
success. But am still curious about "%ls%. All this typing and the question
comes down to what does "%ls" give you? Does it have something to do with
the fact that "fib->fib_FileName[0]" being an address (pointer) therefore
a long, and not an int? Am I going to answer all my own questions?


Thanks again.



-- 
"Better graphics with crayons"                 Michael Figg
Have since switched to oil based paints        DLA Systems Automation Center
but find they really screw up the color        Columbus, Oh.
map and pens!                                  (614)-238-9036