Restricting the scope for the compiler?

Tim Rowledge tim at sumeru.stanford.edu
Mon Jul 15 01:22:44 UTC 2002


"Andreas Raab" <Andreas.Raab at gmx.de> is claimed by the authorities to have written:

> One thing I forgot: You might want to introduce your own "undeclared"
> repository.
ooh, good point. I think I probably want to make sure that undeclared is
an error, and force questions writers to declare everything properly. I
suppose it _might_ be interesting to do the Workspace-like thing, but
explaining about that to the typical college tutor is probably too much
work. I'm definitely torn between keeping it as restricted as possible
for safety, explainability and simplicity and making it as flexible as
possible for cleverness. 

> > Whilst looking around that area I spotted a couple of odd seeming
> > methods and simply added a comment to mark what seems odd to me.
I realise that I almost certainly don't need to care about those
methods, but it always seems wise to raise a reminder to whomsoever it
may concern when spotting such 'this is temporary, get rid of it'
comments!

tim
PS if anyone would like to try out the current demo of this stuff,
Stephen Pair has very generously put up a version at
http://tim.pairhome.net/seaside/basicDemo . I'd very interested to hear
of any problems. I.E. users will almost certainly have to change the
caching setting of their browser to re-fetch every time, since Seaside
uses dynamically created pages and this seems to confuse I.E.

-- 
Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
Useful random insult:- Sharp, like stone in river.  Swift, like tree through forest.




More information about the Squeak-dev mailing list