Bernard Normier
Bernard Normier
The protocol tracing shows request IDs, which in theory allows you to match a response (reply with ice1) to a request. However, the scope of each request ID is a...
In programming languages without GC, such as C++ and Swift, Ice's default behavior should be to reject during unmarshaling operation parameters and return values that create cycles. Then, if an...
Ice for Swift currently creates and drains an autorelease pool for each API that can throw an Ice runtime exception from IceImpl (written in ObjC++), because the throwing of such...
The `cpp:const` metadata makes the mapped servant's member function const, and was introduced years ago when nonmutating was deprecated and replaced by two metadata directives - nonmutating and cpp:const. Since...
The Glacier2 router currently (3.7) does not provide a flow control mechanism: if the forwarded-to server or client (for callbacks) is slow, requests are queued in the router. There is...
In Ice 3.7 and earlier, we have two types of exceptions, both directives from the base abstract Ice::Exception: - user exceptions - run-time exceptions aka local exceptions See https://doc.zeroc.com/ice/3.7/the-slice-language/interfaces-operations-and-exceptions/run-time-exceptions and ...
These features were deprecated in Ice 3.7 and needs to be remove to implement https://github.com/zeroc-ice/ice/issues/611.
- [x] remove Ice for Ruby - [x] clone the cpp "core" into cpp98 and update the build of cpp98-based language mappings (Python, PHP) to use cpp98 - [x] remove...
There is currently not enough metadata validation in the Slice compilers.
Affects Ice 3.7 The [Slice deprecate metadata](https://doc.zeroc.com/ice/3.7/the-slice-language/deprecating-slice-definitions) applies to various Slice definitions and currently affects only the generated code. If you use a Slice definition marked "deprecate" in another Slice...