ignore previous e-mail on the subject. there was a local variable named 'bufcall' in the very same function to keep track of allocb failures and it was causing all the trouble :-(
-----Original Message----- 
From: Gurol Akman
Sent: Friday, March 12, 2004 12:29 PM
To: '[EMAIL PROTECTED]'
Subject: lis_bufcall causes compilation error

i ran into a compilation problem with the lis_bufcall (LiS-2.16.18; gcc 2.95.4).
 
    lis_bufcall(128, BPRI_MED, foo, 0);
 
wouldn't compile & complain about "called object is not a function" whereas
 
    lis_esbbcall(BPRI_MED, foo, 0);
 
would compile just fine. did anyone encounter a similar incidence? thanks,
 
GA
 

Reply via email to