You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the great library! We've been running it in production for three or four years with great success.
It looks like the change (bd9048e) to use queue:queue() as a type rather than plain queue() might have broken the build on releases older than R17:
ERLC apns.erl apns_queue.erl apns_sup.erl apns_connection.erl
src/apns_queue.erl:32: referring to built-in type queue as a remote type; please take out the module name
src/apns_queue.erl:111: referring to built-in type queue as a remote type; please take out the module name
make: *** [ebin/apns.app] Error 1
It looks like the OTP team knew this would be a backwards-incompatible change and introduced a compiler option to suppress the warning, which might be more appropriate than switching to the new type (at least until R18 is released): http://erlang.org/pipermail/erlang-questions/2014-March/078081.html
If support for older releases (R14, 15, and 16, as defined in the rebar.config) is still desired, is it possible to use a preprocessor guard around the new types? We don't use types in our Erlang app, so I'm unsure here.
Thanks for the great library! We've been running it in production for three or four years with great success.
It looks like the change (bd9048e) to use
queue:queue()
as a type rather than plainqueue()
might have broken the build on releases older than R17:It looks like the OTP team knew this would be a backwards-incompatible change and introduced a compiler option to suppress the warning, which might be more appropriate than switching to the new type (at least until R18 is released): http://erlang.org/pipermail/erlang-questions/2014-March/078081.html
If support for older releases (R14, 15, and 16, as defined in the
rebar.config
) is still desired, is it possible to use a preprocessor guard around the new types? We don't use types in our Erlang app, so I'm unsure here.Here are the build results from three OTP versions: https://travis-ci.org/eleostech/apns4erl/builds/67406167
The text was updated successfully, but these errors were encountered: