Imagine you have some C code like this - FOPEN (,0,4,-myreclen, , , ,10, ,reccount); That works fine on MPE and you can even use the #pragma intrinsic FOPEN on HPUX and it seems to parse those pesky ", , " bits. But what if you're using Visual Studio or some other UNIX? I don't think there's even some sneaky way around it with #defines or var args. Any ideas? I think I'm going to have to convert all intrinsic calls manually to something like - FOPEN ("0111000101", MISSING_P,0,4,-myreclen,MISSING_P , MISSING_P, MISSING_P,10, MISSING_P,reccount); The first parameter tells me which parameters are used and MISSING_P is just defined as zero or something. But that's going to be pretty horrible. Any better ideas? I know FOPEN is going to be missing but at this stage I'd just like to compile the code and worry about replacing FOPEN later. Thanks. Peter -- http://www.beluga.freeserve.co.uk * To join/leave the list, search archives, change list settings, * * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *