[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hid
|
From: |
dak |
|
Subject: |
Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden) |
|
Date: |
Mon, 16 Feb 2015 07:56:10 +0000 |
On 2015/02/15 19:54:19, david.nalesnik wrote:
Please review. Thanks!
"Needing to determine the name of a grob" should actually rarely be
necessary: the pervasive information connected to the functionality of a
grob is rather its interfaces. That's the usual criterion for deciding
whether to deal with a particular grob. Relaying on the name makes it
harder to create variants of existing grobs.
https://codereview.appspot.com/203090043/
- Make Grob::name accessible to Scheme (issue 203090043 by address@hidden), david . nalesnik, 2015/02/15
- Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden),
dak <=
- Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden), david . nalesnik, 2015/02/16
- Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden), Paul Morris, 2015/02/16
- Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden), David Kastrup, 2015/02/16
- Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden), Paul Morris, 2015/02/16
- Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden), David Kastrup, 2015/02/16
- Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden), David Nalesnik, 2015/02/16
- Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden), David Kastrup, 2015/02/16
- Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden), David Nalesnik, 2015/02/16
- Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden), Paul Morris, 2015/02/16
- Re: Make Grob::name accessible to Scheme (issue 203090043 by address@hidden), David Nalesnik, 2015/02/16