Re: Declarative constraints in practical terms

From: dawn <dawnwolthuis_at_gmail.com>
Date: 6 Mar 2006 08:24:56 -0800
Message-ID: <1141662296.045812.323800_at_u72g2000cwu.googlegroups.com>


x wrote:
> "dawn" <dawnwolthuis_at_gmail.com> wrote in message
> news:1141230300.386065.194130_at_v46g2000cwv.googlegroups.com...
> > x wrote:
> > > "dawn" <dawnwolthuis_at_gmail.com> wrote in message
> > > news:1141227907.113061.191620_at_t39g2000cwt.googlegroups.com...
> > >
> > > > Then at the top level, what we are doing when we write software is a
> > > > command.
> > >
> > > We think it is a command.
> > > The computer might think it is not. :-)
> >
> > Yes, I can see that perspective. We can write statements that complete
> > the machine. Snooze.
>
> Draco dormiens nunquam titillandus

I had to look that one up. "Never tickle a sleeping dragon." And yet, with that, you went and did it anyway. cheers! --dawn Received on Mon Mar 06 2006 - 17:24:56 CET

Original text of this message