On 16 Mai, 23:33, Fredrik Johansson <fredrik.johans...@gmail.com>
wrote:
> On Sat, May 16, 2009 at 1:29 PM, Ondrej Certik <ond...@certik.cz> wrote:
>
> > On Sat, May 16, 2009 at 1:00 PM, Aaron S. Meurer <asmeu...@gmail.com> wrote:
>
> >> Maple also uses BesselJ, and I couldn't find a spherical function in
> >> the help, but I know little about Bessel functions, so I could have
> >> missed it.  I think that this is best.  Typing underscores is too
> >> difficult, but just jn is too ambiguous.  It also allows for expansion
> >> to BesselI, BesselK, and BesselY, and they would all be grouped
> >> together in dir().  I don't know if uppercase BesselJ or lowercase
> >> besselj would be better.  Typing dir() in isympy, seems to have a mix
> >> of both upper and lower case named functions, with special functions
> >> in both cases (Heaviside, gamma, zeta).
>
> > I was just thinking about this too. Basically I think we should stick
> > to Python convention and that's it. Python convention is to use
> > CamelCase() for classes and lower_case_with_underscores() for
> > functions. Most of the things are implemented as classes in SymPy,
> > thus it should just be BesselJ, Heaviside, Gamma, Zeta, etc.
>
> As pointed out before, a big advantage of this convention is that it
> can be made absolutely consistent while avoiding clashes with
> Python builtins. So we can have Sum() without shadowing Python's sum(),
> Abs() without shadowing abs(), etc.

+1 for using camel case internally for functions, which would be
consistent with Mul and friends. However it should be still possible
to use/print the currently used lower case equivalent.

Vinzent
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sympy" group.
To post to this group, send email to sympy@googlegroups.com
To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sympy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to