[ET Trac] #2752: Parameter file parser generates illegal (?) C code

[Roland Haas]

#2752: Parameter file parser generates illegal (?) C code

 Reporter: Erik Schnetter
   Status: new
Milestone: 
  Version: 
     Type: bug
 Priority: major
Component: EinsteinToolkit thorn

Changes (by Roland Haas):

component: EinsteinToolkit thorn (was Cactus)

Comment (by Roland Haas):

Most likely this is a “\\phi” \(ie LaTeX syntax\) in one of the parameter descriptions of TwoPunctures\_BBHSF. Those get copied to C strings and will then trigger this.  

The simplest solution is to not use LaTeX code in Cactus description strings \(or double up on the backslash\). A better solution \(in Cactus\)  may to sanitize strings passed in by users, but is only doable if there are not yet thorns that  that double up the backslash already \(right now `grep -rF '\\' arrangements///*.ccl` returns none\).

Cheng-Hsin and Giuseppe are maintainers, but Bitbucket will not let me enter Cheng-Hsin into the assignee field \(even though he is a teammate\) and Giuseppe does not seem to be a team member.

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2752/parameter-file-parser-generates-illegal-c
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.einsteintoolkit.org/pipermail/trac/attachments/20230824/a6119659/attachment.htm>