Arthur Magill a écrit : > Hi Thomas, > Hi Arthur,
> 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). > Thanks for the info. You're certainly right, some OCC C++ code being quite old (just read the license headers in source files). > > __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? > It might be enough to ensure code quality. > 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? > I agree with you: let's trust the user but let's give him a good information. > Cheers, > Cheers, > Arthur > Thomas _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
