From 269208b713da721d832bfc9a75bdfc4da79dcf68 Mon Sep 17 00:00:00 2001 From: eschnett Date: Wed, 9 May 2012 17:00:24 +0000 Subject: Remove outdated language recommendations git-svn-id: http://svn.cactuscode.org/flesh/trunk@4820 17b73243-c579-4c4c-a9d2-2d5706c11dac --- doc/UsersGuide.pdf | Bin 789863 -> 789718 bytes doc/UsersGuide/ApplicationThorns.tex | 16 ++++------------ 2 files changed, 4 insertions(+), 12 deletions(-) (limited to 'doc') diff --git a/doc/UsersGuide.pdf b/doc/UsersGuide.pdf index a627b66b..82438953 100644 Binary files a/doc/UsersGuide.pdf and b/doc/UsersGuide.pdf differ diff --git a/doc/UsersGuide/ApplicationThorns.tex b/doc/UsersGuide/ApplicationThorns.tex index 54ef1499..59d93373 100644 --- a/doc/UsersGuide/ApplicationThorns.tex +++ b/doc/UsersGuide/ApplicationThorns.tex @@ -832,7 +832,7 @@ The makefile is passed the following variables \item [\texttt{\$(THORN)}] the thorn name -\item [\texttt{\$(SCRATCH\_BUILD)}] the scratch directory where Fortran 90 module +\item [\texttt{\$(SCRATCH\_BUILD)}] the scratch directory where Fortran module files should end up if they need to be seen by other thorns. \item [\texttt{\$(NAME)}] the name of the library to be built @@ -1571,23 +1571,15 @@ returned to the original state. When you start writing a new thorn, the first decision to make is which programming language to use. The source code in Cactus thorns -can be written in any mixture of Fortran 77, Fortran 90, -C or C++. The following points should be considered when -choosing a language to work in +can be written in any mixture of C, C++, CUDA, or Fortran. +The following points should be considered when +choosing a language to work in: \begin{itemize} \item All functions designed for application thorn writers are available in all languages, however, some interfaces for infrastructure thorn writing are only available from C or C++. -% This is no longer relevant? -%\item If you are writing in Fortran, use \texttt{F77} if you want -% to distribute your code to people who may not be able to afford -% to buy proprietary Fortran 90 compilers. - -\item Stick to C rather than C++, unless you really need - features from C++, this will help you with portability. - \end{itemize} Whatever language you choose, if you want your thorn to be portable, and -- cgit v1.2.3