In article <005e01c47b2d$9c0dee80$6700a8c0 at computer>, "Edward K. Ream" <edreamleo at charter.net> wrote: > The major concern I have with '@' syntax as it relates to Leo is the > potential for ongoing and never-ending conflicts between Leo's directives > and @x constructs in Python. I don't know what Leo is, but the usual solution to this sort of problem is to introduce some kind of quoting convention, e.g. @@ gets passed through as a single @ to Python, any other @something gets treated as a Leo directive. Is there some reason that wouldn't work? -- David Eppstein Computer Science Dept., Univ. of California, Irvine http://www.ics.uci.edu/~eppstein/
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