Re: Declarative constraints in practical terms
Date: Tue, 7 Mar 2006 09:12:21 +0200
Message-ID: <dujbop$r48$1_at_emma.aioe.org>
"dawn" <dawnwolthuis_at_gmail.com> wrote in message
news: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
Well, I live in the land of the dragons :-) Received on Tue Mar 07 2006 - 08:12:21 CET