Jose

We get this warnigs when building for macOS ```clang: warning: -framework ExternalAccessory: 'linker' input unused [-Wunused-command-line-argument] clang: warning: -framework ExternalAccessory: 'linker' input unused [-Wunused-command-line-argument] ``` probably because iAP sources are...

The PHP NuGet packages we build should depend on the corresponding C++ NuGet package instead of copy the Ice for C++ binaries

The [checkcode ](https://www.mathworks.com/help/matlab/ref/checkcode.html)method can be use to check for problems in MATLAB code, we should integrate this with our MATLAB builds

The TypeScript test suite only runs with NodeJS, we should allow to run it with browsers. https://github.com/zeroc-ice/ice/blob/8a57c50c1a9773149ed82471cb9e70ae4ef276d8/scripts/Util.py#L3900-L3901

https://github.com/zeroc-ice/ice/commit/54a40faf6ab1351598bad7e78169192029b94bcd After IceStorm service is ported to C++11 we can remove this workaround

I C# we were using null terminated arrays for the property names, that is not required. We can use foreach or Array.Length in C# without need to check for null...

In Swift the call on a well-known proxy won't be collocated because Swift has its own ASM and collocation for well-known proxies rely on the ASM from the C++ object...

Consider adding ssl support for NodeJS

2

Adding support SSL endpoints to NodeJS shouldn't be to difficult, basically we can keep using TcpTransceiver and use `tls.connect` for secure endpoints. One issue with keeping the implementation align with...

We basically need an extra directory with the module name, inside it we put module-info and sources in the package structure. This should allow to get rid of the workaround...

Add IceSSL interoperability test

1

We can add a new IceSSL test to check for interoperability issues beween the different IceSSL implementations, unlike IceSSL/configuration where client/server use the same IceSSL implementation, the interoperability test will...