Jack Jansen wrote:
>
> > The basic syntax in the above examples is:
> >
> > "pragma" NAME "=" (NUMBER | STRING+)
> >
> > It has to be that simple to allow the compiler use the information
> > at compilation time.
>
> Can we have a bit more syntax, so other packages that inspect the source
> (freeze and friends come to mind) can also use the pragma scheme?
>
> Something like
> "pragma" NAME ("." NAME)+ "=" (NUMBER | STRING+)
> should allow freeze to use something like
>
> pragma freeze.exclude = "win32ui, sunaudiodev, linuxaudiodev"
>
> which would be ignored by the compiler but interpreted by freeze.
> And, if they're stored in the __pragma__ dictionary too, as was suggested
> here, you can also add pragmas specific for class browsers, debuggers and such.
Hmm, freeze_exclude would have also done the trick.
The only thing that will have to be assured is that the
arguments are readily available at compile time. Adding
a dot shouldn't hurt ;-)
--
Marc-Andre Lemburg
______________________________________________________________________
Business: http://www.lemburg.com/
Python Pages: http://www.lemburg.com/python/
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