Once there was an research done in PARC about so-called "Aspect-Oriented Programming". The idea was to describe different aspects of the problem (in our case the business logic and the error handling) in different domain-specific languages, then use "compiler" to combine the two into actual executable code. As far as I know, the idea never got further beyond research stage.
In any case, it's the only alternative to error codes and exceptions I've ever seen.
It doesn't have UDT, but UDT support was discussed in the past IIRC.
UDT is meant for high-throughput high-latency links. Transports used in 0MQ so far are TCP (generic low volume transport) and PGM reliable multicast (high-volume, low-latency on LAN).
Slashdot Mirror
Once there was an research done in PARC about so-called "Aspect-Oriented Programming". The idea was to describe different aspects of the problem (in our case the business logic and the error handling) in different domain-specific languages, then use "compiler" to combine the two into actual executable code. As far as I know, the idea never got further beyond research stage. In any case, it's the only alternative to error codes and exceptions I've ever seen.
It doesn't have UDT, but UDT support was discussed in the past IIRC. UDT is meant for high-throughput high-latency links. Transports used in 0MQ so far are TCP (generic low volume transport) and PGM reliable multicast (high-volume, low-latency on LAN).