Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can use the preprocessor to print out the file name and line number. You might want take advantage of the predefined preprocessor symbols <code>__LINE__</code> and <code>__FILE__</code>. Here's an example:</p> <p>A preprocessor macro is defined in header file (so that it can be used in multiple locations), call it <strong>errormsg.h</strong>:</p> <pre><code>#define ERRORMSG(msg) write(0,'("There was an error at ",I4," in file ",/,A,/,"Error message: ",A)') __LINE__,__FILE__,msg </code></pre> <p>Then you can include this header file in your program, library or module files, for example:</p> <pre><code>#include "errormsg.h" program main ERRORMSG("not really an error...") call foo() end program subroutine foo() ERRORMSG("not an error too!") end subroutine </code></pre> <p>The <code>ERRORMSG("not really an error...")</code> seems like weird syntax for fortran code, but it get's replaced by the c-preprocessor using the macro definition. So when this is compiled, it looks like:</p> <pre><code>write(0,'("There was an error at ",I4," in file ",/,A,/,"Error message: ",A)') __LINE__,__FILE__,"not really an error" </code></pre> <p>For my <code>ERRORMSG</code> macro, I chose to use the 0 file unit to print to stderr. You obviously have the freedom to write the message how ever you like, as long as it results in syntactical correct FORTRAN code. </p> <p>Getting this to compile requires you to pass flags to the compiler, and they differ slightly from compiler to compiler. This worked for me, for example:</p> <pre><code>gfortran -cpp -o errorTest errorTest.f90 </code></pre> <p>That is, for gfortran, <code>-cpp</code> invokes the c-preprocessor before compiling. The output from the above program looks like this: </p> <pre><code>There was an error at 5 in file errorTest.f90 Error message: not really an error... There was an error at 13 in file errorTest.f90 Error message: not an error too! </code></pre> <p>This might have the effect you are looking for, especially if you write only one subroutine per file. </p>
    singulars
    1. This table or related slice is empty.
    1. POFortran query and print out function or subroutine name
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USYann
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWith gfortran and some other compilers, you can also invoke the C-preprocessor by using filetype "F90", with an upper-case "F".
      singulars
      1. PO
      1. USM. S. B.
    2. COThanks! This is an interesting idea. Unfortunately, it will not work for my case, because for my small, self-contained projects I prefer to have a single file with the code. But what you've suggested it is a handy tool for future exploration.
      singulars
      1. PO
      1. USdrlemon
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload