summaryrefslogtreecommitdiff
path: root/doc/FAQ
diff options
context:
space:
mode:
authorallen <allen@17b73243-c579-4c4c-a9d2-2d5706c11dac>2003-03-04 08:07:29 +0000
committerallen <allen@17b73243-c579-4c4c-a9d2-2d5706c11dac>2003-03-04 08:07:29 +0000
commite27f2a4b3aa5f42ca4d4ad6cd6947881556f8bd2 (patch)
tree125fb70e3a0b5f713848a4890ee47b746397081e /doc/FAQ
parent4cbbc85e724bd88e51ab120ad808665c8a9c7ade (diff)
F9 The documentation says that Cactus parameters are read-only, but I
can trivially change the value of a parameter in the Fortran source code of my thorn. Although changing parameters in Fortran is possible (we haven't thought of an easy way to enforce read-only parameters) it is not supported and should not be done! git-svn-id: http://svn.cactuscode.org/flesh/trunk@3158 17b73243-c579-4c4c-a9d2-2d5706c11dac
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ15
1 files changed, 14 insertions, 1 deletions
diff --git a/doc/FAQ b/doc/FAQ
index 8602075b..38b7c5d8 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
Cactus Code Frequently Asked Questions
-$Header: /mnt/data2/cvs2svn/cvs-repositories/Cactus/doc/FAQ,v 1.59 2003-02-19 11:11:16 allen Exp $
+$Header: /mnt/data2/cvs2svn/cvs-repositories/Cactus/doc/FAQ,v 1.60 2003-03-04 08:07:29 allen Exp $
Also available at http://www.cactuscode.org/Documentation/FAQ
@@ -250,6 +250,11 @@ F7 Why don't you use compilers mpicc, mpiCC etc when they exist on parallel
F8 How does Cactus manage to so seamlessly call Fortran routines from
C, and vice versa?
+F9 The documentation says that Cactus parameters are read-only, but I
+ can trivially change the value of a parameter in the Fortran source
+ code of my thorn.
+
+
------------------------------------------------------------------------------
Documentation:
@@ -1307,6 +1312,14 @@ F8 How does Cactus manage to so seamlessly call Fortran routines from
maintained in the file src/include/cctk_FortranString.h. At the moment
we have macros for one, two or three strings in an argument list.
+F9 The documentation says that Cactus parameters are read-only, but I
+ can trivially change the value of a parameter in the Fortran source
+ code of my thorn.
+
+ Although changing parameters in Fortran is possible (we haven't thought
+ of an easy way to enforce read-only parameters) it is not supported and
+ should not be done!
+
------------------------------------------------------------------------------
Documentation: