[yoshimi] Re: reference to 'lock' is ambiguous
- From: Will Godfrey <willgodfrey@xxxxxxxxxxxxxxx>
- To: yoshimi@xxxxxxxxxxxxx
- Date: Thu, 26 Oct 2017 13:35:25 +0100
On Thu, 26 Oct 2017 17:38:28 +0800
blubee blubeeme <gurenchan@xxxxxxxxx> wrote:
I get compiler errors relating to this 'lock' issue.
Looking at the code it seems that there's namespace pollution between the
enum definition:
typedef enum { init, lock, unlock, destroy } lockset;
and the multithreading lock.
I appended enum_ to the variables and made these diffs.
<snip>
would those changes or something similar be acceptable?
Yes, these seem quite reasonable. It would seem your compiler is more fussy
than gcc!
Eventually the locks will go completely (there are far fewer than there used to
be) but I'll patch this in as an iterim measure.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Yoshimi source code is available from either:
https://sourceforge.net/projects/yoshimi
Or:
https://github.com/Yoshimi/yoshimi
Our list archive is at:
https://www.freelists.org/archive/yoshimi
To post, email to yoshimi@xxxxxxxxxxxxx
Other related posts: