Shan's Page

Mixed-mode processes and IPC

Mixed-mode processes, because of their ability to call both Win32 subystem and subsystem libraries, can use both posix and windows I nter P rocess C ommunication mechanisms. This ability makes mixed-mode processes far more capable in terms of IPC abilities

Debugging mixed-mode applications

32 bit Mixed mode applications can be debugged using both Gdb and Visual studio debugger. (Since there is no 64 bit gcc suite available for SUA, 64 bit mixed mode apps cant be debugged using gdb - VS debugger is the only option.) There is caveat that

Mixed-mode programming paradigms… part 2.

In part 1 , I had written about how mixed-mode code can be written using the ‘inline’ approach. In this post I will write about the second approach. SUA Application that links to a custom Win32 dll which exposes functions and data whose datatypes are

Mixed-mode programming paradigms… part 1.

Like I alluded to in the post Using win32 GUI from posix code using mixedmode. , there are more than one way to write mixed mode programs . There are atleast two distinct approaches that we can take when we write code that transgresses both posix and

Invoking win32 GUI from posix code using mixedmode.

In the last post , i was talking about mixed-mode and the various scenarios that it enables. In this post, let us look at a small sample app that would make it more clear. the goal of our sample app is to throw a win32 windows from posix code. There are

Mixedmode - easy way to extend your applications!

Mixed-mode refers to the ability of code running on the Subsystem for UNIX Applications (SUA) to use native windows libraries. Anyone familiar with SFU or SUA would know that one can port POSIX compliant code over to SFU/SUA. Though this enables one to