[Stk] Register keyword is deprecated
Ariel Elkin
arielelkin at gmail.com
Sat Apr 5 13:41:16 PDT 2014
OK, I made a pull request to that effect:
https://github.com/thestk/stk/pull/13
On 5 Apr 2014, at 21:31, Gary Scavone <gary at ccrma.stanford.edu> wrote:
> No problem. That is another left-over from the days when computers were much slower and we were really worried about algorithm efficiency.
>
> —gary
>
> On Apr 5, 2014, at 4:07 PM, Perry Cook <prc at cs.princeton.edu> wrote:
>
>> I'm all for removing it in all cases. Just one throw of any
>> level of -O# optimization gives the compiler the right to
>> make these decisions for us anyway. The variety of
>> Processor architectures with registers numbering from
>> 2 to dozens means we'll generally not make the best
>> choices, but the compilers know what to do better than
>> we.
>>
>> Prc
>>
>> Sent from my iPad :-)
>>
>>> On Apr 5, 2014, at 1:00 PM, Ariel Elkin <arielelkin at gmail.com> wrote:
>>>
>>> Hey all,
>>>
>>> Several Stk classes such as BeeThree, FMVoices, HevyMetl, as well as Stk.cpp make use of the “register” storage class specifier.
>>>
>>> According to the latest C++ standard, “the use of the register keyword as a storage-class-specifier (7.1.1) is deprecated”
>>> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3797.pdf
>>> page 1242
>>>
>>> Compilers such as LLVM v5.1 have picked up on this and are starting to complain heavily...
>>>
>>> So anyone has an objection to getting rid of "register”?
>>>
>>> Cheers
>>>
>>> Ariel
>>>
>>> _______________________________________________
>>> Stk mailing list
>>> Stk at ccrma.stanford.edu
>>> http://ccrma-mail.stanford.edu/mailman/listinfo/stk
>>
>> _______________________________________________
>> Stk mailing list
>> Stk at ccrma.stanford.edu
>> http://ccrma-mail.stanford.edu/mailman/listinfo/stk
>
More information about the Stk
mailing list