Hi Thomas,
Glad you're happy with the idea.
> 2.Two things to check before going on
> Before this is commited to the subversion repository, I would like
> however to know where does this naming convention (OpenCascade I mean)
> comes from? why doesn't OpenCascade API use C++ namespaces? Certainly
> have to post a message on the OCC forum.
>
Using namespaces in C++ in the early 90s was pretty hairy - some compilers did,
some didn't. I'd guess the OCC guys decided to go with something that would
compile everywhere (same story as the lack of templates).
> __But__: imagine a pythonOCC user do:
> from OCC.BRepPrimAPI import *
> MakeBox(...)
> The code will quickly be unreadbable (from which module comes the
> MakeBox object)?
I'm not enough of a python user to know if this is a real problem. It seems
like
something that will lead to trouble, but can we just advise users not to do it?
Most languages let you shoot yourself in the foot if you really want to*, but I
have no idea if this is a case of bad style, or a reasonable construct that
will
cause trouble?
Cheers,
Arthur
* have you ever noticed that Matlab lets you redefine i? Doesn't sound like a
big deal, until you realise that sqrt(-1)!=i, and all your complex math has
just
gone south!
_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users
