🚀 go-pugleaf

Colin Johnson <colin@pangaea.com.au> wrote:

> Jan@Bytesmiths.com (Jan Steinman) wrote:
> >In article <31711755.328F@charm.net>, Bob Arning <arning@charm.net> wrote:
> >
> >> Jan Steinman wrote:
> >...
> >> > Ready, set, go (standard disclaimer, typed in off the top of my head):
> >> > 
> >> > | pi n |
> >> > pi := 0.
> >> > n := "number of hex digits of precision desired"
> >> > 1 to: n do: [:i | pi := pi +
> >> >   ((1 / (16 raisedTo: i) *
> >> >     ((4 / ((8 * i) + 1)) +
> >> >     (2 / ((8 * i) + 4)) +
> >> >     (1 / ((8 * i) + 5)) +
> >> >     (1 / ((8 * i) + 6))))].
> >> > pi
> >> > 
> >> > Okay, has your C compiler finished yet? :-)
> >...
> >> Your standard disclaimer notwithstanding, it would be a more impressive 
> >> example if it actually worked. Where does the missing right paren go?
> >
> >Oops! I separated it into one factor and four terms, but I guess I wasn't
> >counting right. Without the Smalltalk paren-matcher, I'd have to guess it
> >goes before the square bracket. Sorry!
> >
> > : Jan Steinman <mailto:Jan@Bytesmiths.com>
> > : Bytesmiths, the Smalltalk specialists <http://www.bytesmiths.com>
> > : "This is witty signature 1 of 47,288."
> 
> 
> Of course, guys, the wonderful thing about Smalltalk is that if Jan's code 
> had been typed into a workspace and executed, the error (a simple typo) 
> would have been detected immediately. What about the poor C++ coder? Fix 
> it, then compile -again-! :-)
> 
> Regards,
> Col

With an IDE, there's not that much difference anymore.  You're compiling
from the editor vs. executing from the editor.  And a smart editor would
have made the mismatch obvious as it was typed.  What about the poor
Smalltalk programmer?  Fix it, then execute -again-!  :-)

Doug Bell
dbell@shvn.com