[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name acces
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme |
Date: |
Mon, 16 Feb 2015 18:55:44 +0000 |
Comment #8 on issue 4290 by address@hidden: Patch: Make Grob::name
accessible to Scheme
https://code.google.com/p/lilypond/issues/detail?id=4290
From #4:
"Hmm, I think what I will end up doing is rewriting the function to return
a symbol. Grob::name takes a symbol, converts it into a string usable by
C++, then
ly:grob-name converts this string into a Scheme type. I'd hate to write
another function which converts that Scheme string back into the symbol we
started out with! It makes a lot of sense to simply return the symbol, and
if someone really wants a string--and, come to think of it, I don't believe
I ever have--use symbol->string."
The new patch returns a symbol instead of a string. I opted not to attempt
a conversion of the C++ string returned by Grob::name back into the Scheme
symbol we began with.
(By the way, a very circuitous route is used for ly:context-name.)
--
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
- [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/15
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/15
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/15
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/15
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/15
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/15
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/16
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/16
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme,
lilypond <=
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/17
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/19
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/19
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/19
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/19
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/20
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/22
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/25
- Re: [Lilypond-auto] Issue 4290 in lilypond: Patch: Make Grob::name accessible to Scheme, lilypond, 2015/02/25