Hi Mark, There's currently no way to avoid the warnings except to disable them with pragmas or compiler flags.
For example: #pragma GCC diagnostic push #pragma GCC diagnostic ignored "-Wdeprecated-declarations" // ... call importCap here ... #pragma GCC diagnostic pop I would like to remove these eventually, though... How sticky is this embedded board software? Is it likely to be around for years to come, without updates? If so maybe we're stuck with these. FWIW, importCap/exportCap were introduced in 0.4 (2013) and deprecated in 0.5 (2014), so they've now spent far more time deprecated than not... -Kenton On Tue, May 2, 2017 at 1:52 AM, <mark.good...@gmail.com> wrote: > I'm connecting to some embedded hardware running both client and server > EzRpc interfaces with the old importCap/exportCap methods and I want to > connect to them without any warnings in my code about depreciated > interfaces. > > Is it possible to have a client and server which have the new > getMain<.*>() functionality talk to server and client using the original > methods? > > I don't have access to change the embedded board software. > > -- > You received this message because you are subscribed to the Google Groups > "Cap'n Proto" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to capnproto+unsubscr...@googlegroups.com. > Visit this group at https://groups.google.com/group/capnproto. > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to capnproto+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/capnproto.
