[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 4376 in lilypond: Patch: Redefine LY_ASSERT_SM
|
From: |
lilypond |
|
Subject: |
Re: [Lilypond-auto] Issue 4376 in lilypond: Patch: Redefine LY_ASSERT_SMOB to deal with inherited is_smob |
|
Date: |
Thu, 07 May 2015 08:41:26 +0000 |
Updates:
Cc: address@hidden
Comment #4 on issue 4376 by address@hidden: Patch: Redefine LY_ASSERT_SMOB to
deal with inherited is_smob
https://code.google.com/p/lilypond/issues/detail?id=4376
Regarding comment #3: I lean towards stepping ahead here and indeed adding
an LY_ASSERT_DERIVED_SMOB in the series for issue 4357: it removes
awkwardness from code there (and additional awkwardness in a followup
issue) while not touching existing usage. Or rather, hardly touching. It
does make sense to use the same function call for error processing.
The question of whether to fold LY_ASSERT_DERIVED_SMOB with LY_ASSERT_SMOB
eventually would then basically become part of issue 4365.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings