<2> Regards to Bech32 I am trying to compile it on Visual Studio 2017 community edition using c +1+(
https://i.imgur.com/yo5J4Q6.jpg jargon ... hang on (I am running out time) going to ed; this post again ... So I am not sure if it going to compile or not ...since there are some barvarian char set and maybe I only will see the out put at Oktoberfest. (pls relax this is a joke, when we'serious we ARE serious)
I think that this should probably work, mostly. For its user interface, the utility uses POSIX getopt(3) functionality, and also the BSD-style (also available on Linux). I dont know to deal with that on Windows. Otherwise, it is just STDC.
I myself cant test MSVC compilation; for I have no Windows in my house. Please let me know what results you get.
Should there be indicators of demand, I
may try to produce Windows binaries with mingw.
If you need to replace anything with code from WIN32, I strongly suggest that you #define WIN32_LEAN_AND_MEAN. I seem to vaguely also remember some define for Unicode, but I dont remember what it is. If somebody comes up with Windows/MSVC compat code, I may try to abstract that into a separate file. I will
not clutter main files with #ifdefed Windows code, or Windows decorations; I was recently trying to audit a simple cross-platform library where every function is decorated with DLLEXPORT, and that junk makes code unreadable.
Definitely I will try MSVC compilation and I will let you know the results I get. But, ( as my usual academic methodology ) firstly, I need to do a research on system development history. For instance, I know that
is old as Windows NT Kernel ( ). ( I don't know, in my memory Microsoft's Unix reminds me
. Also regards to cryptology and Redmond campus... in general I find a pleasure reading Niels Ferguson, Bruce, and Kohno book ISBN: 978-0470474242
ps-> Nice to see that your *nix flavour is BSD Group ;-) Most of the time I have really nice experience on SDF Public Access UNIX System .. Est. 1987 ...