1 Introduction Traditionally, developing software for both hemispheres has been a diûcult endeavor. Usually, developers have to write two separate applications for both hemispheres. This is an obviously ineûcient approach with multiple problems: " The overall size of the codebase is doubled. " Every single line changes when checking code into source control. " Double the programmers need to be hired (i.e., one team for C and another for C ). ) In code listings 1 and 2 below, we show a simple test case and the traditional two-system development. [C program right-side up] "Northern Hemisphere example" [C program upside down] "Southern Hemisphere example"
https://media.woem.space/media/ed5ad8536a47afc42918908f3c57c3e9ced1f062adf3b8960e9b9f63f607989d.png