[Zpt] Built-ins and Shadows

[Shane Hathaway]

Todd Coram wrote:
> 
> >  Warnings are cool.
> 
> Warnings are warm, errors are hot; clean code is cool ;-)
> 
> Where the warnings go is an interesting problem. Is there a warning/error
> log in Zope? Since editing may not always be done thru the edit form (maybe
> thru webdav + golive or whatever), warning feedback may be difficult. Error
> is easier (munge or annotate the rendered page).

Warnings can be stored in a volatile attribute and displayed to the user
on the edit screen (or perhaps there would just be a link that can get
them to the warnings.)  Note that it's important that it be a volatile
attribute since TALES may change more often than a presentation
template.

> > The problem with errors is that
> > if a new builtin name is ever added, then existing code that
> > happens to have
> > already used that name suddenly becomes illegal "for no reason at
> > all" -- and
> > users hate that.  The usual shadowing rules ensure that their
> > code continues
> > to work, albeit with new warnings; much friendlier.
> 
> What ever happened to the 'sys' prefix that was discussed?

We renamed it "standard".

Shane