+1 for "_SAGE_FUNC". The user should not have to think about the Maxima pre-defined name space unless s/he wants to use a Maxima function:
"When I use a word, it means what I choose it to mean, neither more nor less." -- Humpty-Dumpty On Tuesday, February 26, 2019 at 10:33:23 AM UTC-8, Nils Bruin wrote: > > > > > It's actually very easy: Just as we prefix the print name of a variable > with "_SAGE_VAR_" before feeding it to Maxima in textual form, we can > prefix user-defined functions with, say, "_SAGE_FUNC_" by default. For > functions that should be translated into a meaningful name in maxima we > should of course do that, and we already have infrastructure for that. We > could easily tweak the standard translation to do a little more to avoid > name clashes. > > An argument against it is that error messages emanating from maxima are > almost indecipherable because of the name mangling. However, that already > happens now with the variable names. I don't think doing the same thing > with function names is going to make things that much worse. > > TIcket #13071 is a different issue, by the way. The issue still does exist > and possible fixes are outlined on the ticket. > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
