Dear Andrew!

First I want to thank you very much for the excellent stuff in TIP!
Your work is very useful for me!

With the bug report I didn't want to criticise your work, but every
programmer needs bug reports, isn't it? It was in friendly spirit...

_My_ egoism is as follows: I want to create a LargeIntegers plugin (see
) and wanted to get a feeling of the stability of the existing
interpreter classes (to know where to search if or how to avoid that
something funny happens ;-) ).

And often fast written hints save newbies a lot of work...

Greetings,

Stephan Rudlof


"Andrew C. Greenberg" wrote:
> 
> >But now the following questions arise for me:
> >
> >What's the status and stability of class TestInterpreterPlugin? Any
> >experiences?
> 
> TestInterpreterPlugin is well-tested with respect to external code
> that actually uses the #primitive:parameters:receiver: protocol.
> Obviously, it isn't so well-tested with "traditional" external
> primitive code.  I'll fix the "return self" bug in the next release.
> 
> TIP can generate some redundant checks, which I hope to trap in a
> future version.  I think most good optimizing compilers can pick them
> up in the near term and, if it is a real problem, so can a decent
> GREP-based text editor.
> 
> TIP is certainly the way of the future, making plugin code much
> easier and clearer to write -- but it isn't entirely there yet and
> does have some limitations.
> 
> >A class name with 'Test' inside it doesn't sound very 'final'... But
> >probably it is meant as testbed for to be interpreted plugins or so -
> >but the superclass InterpreterPlugin has a similar functionality and no
> >'Test' inside its name...
> 
> Its what it seems like -- a prototype replacement for the existing
> interpreter -- but it seems to be working just fine.  If its any
> comfort, this is only the second bug report I've gotten since its
> release, and I've only found a few others.
> 
> If you find the "traditional" approach preferable, by all means use
> InterpreterPlugin.  If you wish to use the
> #primitive:parameters:receiver: protocol, TestInterpreterPlugin is
> the only show in town.
> 
> >How to solve the problem 'return self;'?
> >       I know how to solve it manually inside the C-sources, but it is not a
> >real solution.
> >Is it possible that there are newer C-headers with other #DEFINE's or
> >so?
> >       I'm using Squeak 2.6 under Linux ported from Ian Piumarta (nice work,
> >thanks!) and my latest update was NO.: 1671 (Squeak 2.7alpha).
> 
> Be patient, all good things come in time.

-- 
Stephan Rudlof (sr at evolgo.de)
   "Genius doesn't work on an assembly line basis.
    You can't simply say, 'Today I will be brilliant.'"
    -- Kirk, "The Ultimate Computer", stardate 4731.3