Re: printing logical variables as "true" and "false"

"Andy Mai" <mai@xxxxxxxxxxxxxxx> wrote in message
news:dmii1h$pq6$1@xxxxxxxxxxxxxxxxxx

> Are you aware that running the Fortran program in your signature
> produces different results with various compilers?

I may have to change my email address and not include it
in my sig.f90 file because you printed it in public. Thanks
a lot.

--
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end


.

Relevant Pages

  • Re: IVF IA-32 error help
    ... external symbol MAIN_reference in function _main" I am not sure what is ... calling this. ... You can get a message like this from many compilers if you are trying ... "main" Fortran program. ...
    (comp.lang.fortran)
  • Re: Coding style article with interesting section on white space
    ... >the execution of your Fortran program by 25% when you move it from one ... >more depending on how good the optimizers of different compilers happen ... Look at the Fortran compiler benchmarks here: ...
    (comp.lang.python)
  • Re: Why I love python.
    ... > must accept that JIT-compilers are, nevertheless, compilers! ... JITs might compile different code for each time through a ... method if the signature changes dynamically. ...
    (comp.lang.python)
  • Re: Calling C function from Fortran
    ... BAS and BY in your Fortran program. ... (Strings or arrays ?) ... Most compilers add an extra argument to a procedure to pass the length ...
    (comp.lang.fortran)
  • Re: Why I love python.
    ... write Python itself in a Python-subset that can be efficiently ... must accept that JIT-compilers are, nevertheless, compilers! ... > so that it can reuse code when the object types don't change (which ... and a signature for the application is ...
    (comp.lang.python)