Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(7093)

Issue 287350043: Remove Smob::type_p_name_ default

Can't Edit
Can't Publish+Mail
Start Review
Created:
8 years, 1 month ago by dak
Modified:
8 years, 1 month ago
Reviewers:
c_sorensen, Carl, limburgher, carl.d.sorensen
CC:
lilypond-devel_gnu.org
Visibility:
Public.

Description

Remove Smob::type_p_name_ default This was the single most problematic thing across C++ compilers and standards. Foregoing it means a hassle, but using it turned out to be worse.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+26 lines, -12 lines) Patch
M lily/all-font-metrics.cc View 1 chunk +2 lines, -0 lines 0 comments Download
M lily/include/all-font-metrics.hh View 1 chunk +1 line, -0 lines 0 comments Download
M lily/include/listener.hh View 1 chunk +1 line, -0 lines 0 comments Download
M lily/include/paper-outputter.hh View 1 chunk +1 line, -0 lines 0 comments Download
M lily/include/scale.hh View 1 chunk +1 line, -0 lines 0 comments Download
M lily/include/scm-hash.hh View 1 chunk +1 line, -0 lines 0 comments Download
M lily/include/smobs.hh View 1 chunk +5 lines, -12 lines 0 comments Download
M lily/include/translator-dispatch-list.hh View 1 chunk +1 line, -0 lines 0 comments Download
M lily/listener.cc View 1 chunk +2 lines, -0 lines 0 comments Download
M lily/paper-outputter.cc View 1 chunk +2 lines, -0 lines 0 comments Download
M lily/scale.cc View 1 chunk +2 lines, -0 lines 0 comments Download
M lily/scm-hash.cc View 1 chunk +2 lines, -0 lines 0 comments Download
M lily/translator-dispatch-list.cc View 1 chunk +2 lines, -0 lines 0 comments Download
M lily/unpure-pure-container.cc View 2 chunks +3 lines, -0 lines 0 comments Download

Messages

Total messages: 5
Carl
LGTM. Thanks for dealing with this so quickly! Carl
8 years, 1 month ago (2016-03-03 00:48:04 UTC) #1
dak
On 2016/03/03 00:48:04, Carl wrote: > LGTM. > > Thanks for dealing with this so ...
8 years, 1 month ago (2016-03-03 07:23:33 UTC) #2
limburgher_gmail.com
On Thu, Mar 3, 2016 at 1:23 AM, <dak@gnu.org> wrote: > Reviewers: carl.d.sorensen_gmail.com, > > ...
8 years, 1 month ago (2016-03-03 14:19:12 UTC) #3
c_sorensen
On 3/3/16 12:23 AM, "dak@gnu.org" <dak@gnu.org> wrote: >Reviewers: carl.d.sorensen_gmail.com, > >Message: >On 2016/03/03 00:48:04, Carl ...
8 years, 1 month ago (2016-03-03 19:58:59 UTC) #4
dak
8 years, 1 month ago (2016-03-03 22:12:52 UTC) #5
Carl Sorensen <c_sorensen@byu.edu> writes:

> On 3/3/16 12:23 AM, "dak@gnu.org" <dak@gnu.org> wrote:
>
>>Reviewers: carl.d.sorensen_gmail.com,
>>
>>Message:
>>On 2016/03/03 00:48:04, Carl wrote:
>>> LGTM.
>>
>>> Thanks for dealing with this so quickly!
>>
>>> Carl
>>
>>Quickly?  We went months without release because of C++ compiler
>>problems related to this exact type match already once.  And a number of
>>patches.  I don't want to restart this cycle of standard/compiler
>>compliance hunting.
>>
>>This is not "dealing with this so quickly" rather than "throwing in the
>>towel right away this time round".
>
> I've seen you work long enough to know how much it pains you to have
> to do something expedient, rather than right.

It's not wrong, just boorish.  But you don't carry a laser sword into
mud wrestling.  You don't take the chance of running against the
standard committees.  You grit your teeth and walk.

> I appreciate your willingness to find an acceptable expedient
> solution, even though it's not perfect.

It's adequate.  Adequate is good, very good, very excellent good; and
yet it is not; it is but adequate.

-- 
David Kastrup
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b