On Sun, Mar 24, 2013 at 10:35:42AM -0700, tim Rowledge wrote:
> 
> On 24-03-2013, at 9:22 AM, "David T. Lewis" <lewis at mail.msen.com> wrote:
> 
> > On Sat, Mar 23, 2013 at 10:48:49PM -0700, tim Rowledge wrote:
> >> Eliot had the simple but brilliant idea to move the bitblt plugin to be a subclass of SmartSyntaxInterpreterPlugin and just copy my primitivePixelValueAt code into it. It works, at least so far as I can tell from running it and the BitBLt tests in TestRunner.
> >> 
> > 
> > Is that really a good idea? It seems misleading in the sense that it would
> > imply that the rather large B3DEnginePlugin hierarchy is making use of
> > SmartSyntaxInterpreterPlugin, which seems like an unnecessary source of
> > confusion for readers.
> 
> Err, I moved BitBlt not B3D. No clash there.
> 

Cue voice of Gilda Randner ... "never mind!"


> > 
> > I have to admit that I don't really trust SmartSyntaxInterpreterPlugin very
> > much so maybe it's an unfounded concern.
> 
> I think so; I've used the SSIP stuff for decades (eep) with no particular issues. What had simply failed to percolate into my mind was the thought that the 'plain' syntax is inherited as well, so you can use both anywhere under SSIP class. Now I certainly won't claim that there are no possible clashes somewhere in there - but this experiment suggests it works decently.
> 
> 
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Useful random insult:- Calls people to ask them their phone number.
> 
>