On Wednesday, May 4, 2016 at 3:13:21 PM UTC+2, Erik Bray wrote: > > I don't think it's just "syntactic sugar". If anything it's setter > and *especially* getter methods that are backwards, but unfortunately > necessary in languages like Java that don't have a natural way to > interpose in attribute access.
In C++ you could easily implement @property by overloading operator=. But I don't know any example of where its done in the wild. So I don't think that its something thats lacking in the language. Its just that a good C++ API is different from a good Python API. IMHO the basic difference is that you can and should use Python interactively. Whereas the C++ scoping and name lookup rules are fairly hostile to tab completion, e.g. Koenig lookup. Notwithstanding the existence of ROOT, which I'd consider as further evidence that C++ isn't meant to be used interactively... -- 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.
