> For example, if there is later a need or desire to annotate function > arguments individually as well as functions, or individual > statements or expressions, then @ is a better choice. For example > > @RemoteCall > def Ignite(engine @Remote, environment @Copy, thrust @Float): Nooooo..... If @decorator stays in, I fervently hope it won't be taken as a precedent for using @ for other things all over the place. Otherwise we really *will* end up with a language that resembles Perl. Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg at cosc.canterbury.ac.nz +--------------------------------------+
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4