I give up. Maybe it is my search (Windows) but I cannot seem to find the definition of the F77_CALL or F77_NAME macros. Either there are too many matches or the search just doesn't find it. For example where is the source for: F77_CALL(dpotri) ? Thank you. Kevin
F77_CALL, F77_NAME definition
7 messages · rkevinburton at charter.net, Duncan Murdoch, David Winsemius +1 more
On 03/01/2010 9:11 AM, rkevinburton at charter.net wrote:
I give up. Maybe it is my search (Windows) but I cannot seem to find the definition of the F77_CALL or F77_NAME macros. Either there are too many matches or the search just doesn't find it. For example where is the source for: F77_CALL(dpotri) ?
It's your search. The definition is in src/include/R_ext/RS.h. BTW, this sort of question is much more of an R-devel question than an R-help one. Duncan Murdoch
On Jan 3, 2010, at 9:11 AM, <rkevinburton at charter.net> wrote:
I give up. Maybe it is my search (Windows) but I cannot seem to find the definition of the F77_CALL or F77_NAME macros. Either there are too many matches or the search just doesn't find it. For example where is the source for: F77_CALL(dpotri)
G-Search: F77_CALL(dpotri) # second hit https://svn.r-project.org/R/trunk/src/modules/lapack/Lapack.c Given the fact that it occurs in source code module entitled Lapack.c wouldn't the logical assumption be that is is part of that facility? G-Search: Lapack (dpotri) # first hit http://www.netlib.org/lapack/double/dpotri.f (My net searching effort was two Google entries and three URL clicks. You should re-examine your searching strategies. I don't think the fact that I use a Mac is the reason for the relative ease of searching out this information.)
--
David Winsemius, MD Heritage Laboratories West Hartford, CT
On Sun, Jan 3, 2010 at 2:11 PM, <rkevinburton at charter.net> wrote:
I give up. Maybe it is my search (Windows) but I cannot seem to find the definition of the F77_CALL or F77_NAME macros. Either there are too many matches or the search just doesn't find it. For example where is the source for: F77_CALL(dpotri) ?
I'm not sure what the Windows equivalent of 'grep -r F77_CALL .' is, but the developer who wrote lbfgsb.c left a blatant clue which popped up as the third match: ./appl/lbfgsb.c:#include <R_ext/RS.h> /* for F77_CALL */ About three screenfulls later the actual definition itself appeared. If you are going to do a lot of this on a windows box, get cygwin and learn to use the unix utilities in a cygwin bash shell! Barry
On 03/01/2010 9:43 AM, Barry Rowlingson wrote:
On Sun, Jan 3, 2010 at 2:11 PM, <rkevinburton at charter.net> wrote:
I give up. Maybe it is my search (Windows) but I cannot seem to find the definition of the F77_CALL or F77_NAME macros. Either there are too many matches or the search just doesn't find it. For example where is the source for: F77_CALL(dpotri) ?
I'm not sure what the Windows equivalent of 'grep -r F77_CALL .' is, but the developer who wrote lbfgsb.c left a blatant clue which popped up as the third match: ./appl/lbfgsb.c:#include <R_ext/RS.h> /* for F77_CALL */ About three screenfulls later the actual definition itself appeared. If you are going to do a lot of this on a windows box, get cygwin and learn to use the unix utilities in a cygwin bash shell!
I think it's better to use a reasonable text editor here; I used Textpad. I don't think there's anything too special about it, but it does have "Search | Find in files", and I can list the file pattern (obviously *.h for a macro definition), and the folder (R-devel/src on my system), and then I only get six hits: two definitions and 4 uses. That's a lot better than 3 screenfuls. You can also use the Windows search facility to find the file, but I find it clunky, and rarely use it. It does also make it easy to limit the searches in the same way as the above, but it won't show the results as nicely. I'm sure you can do the same thing with grep, but I can never remember the syntax to say to search only in *.h files, whereas with the GUI searches it's easy. Duncan Murdoch
On Sun, Jan 3, 2010 at 3:20 PM, Duncan Murdoch <murdoch at stats.uwo.ca> wrote:
I think it's better to use a reasonable text editor here; I used Textpad. ?I don't think there's anything too special about it, but it does have "Search | Find in files", and I can list the file pattern (obviously *.h for a macro definition), and the folder (R-devel/src on my system), and then I only get six hits: ?two definitions and 4 uses. That's a lot better than 3 screenfuls.
Of course. Emacs + Etags. Then it's about four keystrokes :) Barry
On 03/01/2010 10:32 AM, Barry Rowlingson wrote:
On Sun, Jan 3, 2010 at 3:20 PM, Duncan Murdoch <murdoch at stats.uwo.ca> wrote:
I think it's better to use a reasonable text editor here; I used Textpad. I don't think there's anything too special about it, but it does have "Search | Find in files", and I can list the file pattern (obviously *.h for a macro definition), and the folder (R-devel/src on my system), and then I only get six hits: two definitions and 4 uses. That's a lot better than 3 screenfuls.
Of course. Emacs + Etags. Then it's about four keystrokes :)
But of course to reduce "Search for F77_CALL" to 4 keystrokes you need to be able to do Lempel-Ziv encoding in your head; that's what I hate about Emacs. Duncan