Writing code for human beings: IN, OUT and INOUT

Checking the searches that lead people to this blog revealed that they search for “Radvision INOUT”. Thus, on public demand, I will explain the super-secret-non-more-secret parameter guidelines. From RADVISION’s common type definitions: /* Some "empty" definitions that we can use for readability of the code */ #define IN #define OUT #define INOUT What this simply means is these words are replaced by nothing; they are just indications for the reader, not the compiler. I think mini-comments may be the best (read more...)

By Ran Arad  |  May 8th, 2008  |  Filed under SDKs
Add a comment 

Logs + Scripts = Ownage

At times, I like to keep scores between Development and Customer Support (CS). If a problem is on the customer’s side, a point is awarded to development and if the problem is with our code, a point is awarded to customer support. Then there are the many special cases, for example problems with documentation (points for CS), problems with API design (more points for CS), problems fixed for another customer already (points for Development) problems which are already fixed in (read more...)

By Ran Arad  |  April 14th, 2008  |  Filed under SDKs
Add a comment