Timeline for Writing a language agnostic API?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 4, 2017 at 11:11 | comment | added | rwong | @user3797758 First spend some time with higher-up stakeholders to determine whether future requirements (e.g. next 2 years) will make out-of-process (or, over-the-network) necessary. If in-process is okay, then I'd recommend P/Invoke to a DLL (Windows) or SO (Linux). Basile's answer mentions a lot of tools that can generate wrapper / shim code to make this easier. | |
| Oct 4, 2017 at 11:04 | comment | added | user3797758 | I want to develop it on windows and aim for windows but use tech that can be used on linux too. So if in the future someone wants to run on linux I/they would only (theoretically) have to recompile | |
| Oct 4, 2017 at 11:00 | comment | added | rwong | @BasileStarynkevitch did you not see the word "Windows" prefixed to every phrase where it is applicable? | |
| Oct 4, 2017 at 10:58 | comment | added | Basile Starynkevitch | Yes, but you could at least mention Windows in your answer. Few things apply to Linux unchanged. | |
| Oct 4, 2017 at 10:56 | comment | added | rwong | @BasileStarynkevitch Since you have already listed options for Linux, I think my answer complements the Windows part. Though, I sincerely believe OP is indeed having Windows in mind. Also, my answer contains some options that are OS-agnostic as well. P/Invoke works for non-Microsoft CLI implementations (e.g. Mono, .NET Core, etc.) Let's not hijack OP's question for personal software-political expressions. | |
| Oct 4, 2017 at 10:47 | comment | added | Basile Starynkevitch | Your answer is exclusively Windows centered, and Windows was not exactly mentioned in the question (even if F# or CLR is Windows mostly) | |
| Oct 4, 2017 at 10:46 | history | answered | rwong | CC BY-SA 3.0 |