On Thu, May 01, 2008 at 10:02:27AM -0700, Dave Whipp wrote:
> Brandon S. Allbery KF8NH wrote:
>
>> But there *is* some commonality there, to the extent that both are motion.
>> This is the kind of thing that spawned this discussion, in fact: if what
>> matters is motion, there is no reason *not
Brandon S. Allbery KF8NH wrote:
But there *is* some commonality there, to the extent that both are
motion. This is the kind of thing that spawned this discussion, in
fact: if what matters is motion, there is no reason *not* to substitute
one for the other.
{ draw $gun }: makes a big differ
-- Original message --
From: "John M. Dlugosz" <[EMAIL PROTECTED]>
> Jon Lang dataweaver-at-gmail.com |Perl 6| wrote:
> > On Wed, Apr 30, 2008 at 9:58 PM, Brandon S. Allbery KF8NH
> > <[EMAIL PROTECTED]> wrote:
> >
> >> On May 1, 2008, at 0:53 , chromatic wrote
Jon Lang dataweaver-at-gmail.com |Perl 6| wrote:
On Wed, Apr 30, 2008 at 9:58 PM, Brandon S. Allbery KF8NH
<[EMAIL PROTECTED]> wrote:
On May 1, 2008, at 0:53 , chromatic wrote:
correctness sense. Sadly, both trees and dogs bark.)
Hm, no. One's a noun, the other's a verb.
chromatic chromatic-at-wgz.org |Perl 6| wrote:
This is why roles-as-types is so important: type inferencers can't infer
allomorphism because allomorphism relies on explicitly-marked semantic
meanings.
What is your nomenclature here? "vary in sound without changing its
meaning"?
What are
Jon Lang dataweaver-at-gmail.com |Perl 6| wrote:
John M. Dlugosz wrote:
And you can use CLASS in a role also, confidant that it will be looked up
according to the normal rules when the class is composed using that role,
just like any other symbol that is not found when the role is defined.
U
