|
From: Brian E. <be...@me...> - 2005-08-17 12:49:44
|
Keith MARSHALL <kei...@to...> writes: Thanks for the hints, Keith. > I didn't think the `\n' notation was supported in ANSI FORTRAN-77; > surely you should use `char(10)', for standards conformance. Oh, I didn't know that. But the \n is only treated as two individual characters until it is passed to c isn't it? > (You are probably also aware that strict ANSI FORTRAN-77 conformance > requires all symbol names to be limited to six characters, and free > of case sensitive distinctions. Is it case insensitive or is upper case only? Yes, perhaps I didn't mean ansi as in true ansi. I meant fortran77 using only the extensions supported by most modern compilers. > of the call -- there's no getting away from this, if you want it > to work reliably. OK. > In C, you have to add this yourself. In your example, your > `mexPrintcaller-()' wrapper could append this, for a possibly > cleaner interface. Yes, I don't know why I kept it the other way. > A trick I've used in the past, (I haven't written any FORTRAN code > in years), is to have a FORTRAN function something like Good trick, of course I should just look for non-blanks from the end. -- Brian (remove the sport for mail) http://www.et.web.mek.dtu.dk/Staff/be/be.html http://www.rugbyklubben-speed.dk |