Unfortunately I will be distributing it in the source code form, since most people will likely want to implement their own features. So there is no way I can limit target audience, and Russian are known to pirate software, ignoring the license.
I think USA made the wrong decision by lifting the ban on exporting any computer technologies to Russia. Because if Russians have no computers, they can't run any software, including the one powering their nukes.
>>13 Nash C follows the original C's KISS principle and is fully compatible with C99. For example, templates are implemented through the improvement to the C macroprocessor, instead of bringing up additional turing complete language with broken semantics. Also, you can't compile the existing C99 code with C++ compiler, but you can Nash C: it is just as simple as modifying the Makefile to preprocess the file with NCC.
Name:
Anonymous2021-04-10 10:56
>>16 Nash C is also binary compatible with C99 and allows stuff like maintaining metadata to expose all the internals to another language (in my case Symta).
Name:
Anonymous2021-04-10 15:33
New feature - rewriting the symbols during the AST traversal: #macro(a) name_@{typeof a}(); ... macro(x);
would call `name_int` if `x` has type int, or `name_int_ptr`.
not exactly C++/Java generics, result is rather similar, while the implementation is completely exposed to the user.
AFAIK, C99 doesn't use the @ character, so it can be used freely. The `$` is a bit more tricky, since both assemblers and C++ use it for different purposes, therefore it have to be passed to the C99 compiler unchanged, as part a symbol.
`macro` is the name of the macro being defined. #define is the preprocessor directive. `#` defines a macro name. I found it bit cumbersome to write `#define x 123`, so I prefer writing "#x 123". That is my personal macroprocessor NCM, it also allows some more advanced stuff, like gensyms and scoped macros.
Name:
Anonymous2021-04-11 13:38
>>25 will you share source? what happens if you do int &&x;
https://www.nbcnews.com/politics/politics-news/end-child-marriage-u-s-you-might-be-surprised-who-n1050471 ✞🐘✞ End child marriage in the U.S.? You might be surprised at who's opposed ✞🐘✞ Sept. 8, 2019 ✞🐘✞ Conservatives have found some surprising allies as they fight efforts to raise the marriage age. ✞🐘✞ A bill that would have ended child marriage in Idaho — which has no minimum age for couples who want to wed — died in the Statehouse this year. Republican lawmakers, who control the Legislature, opposed it, including state Rep. Bryan Zollinger, who said it "went too far." ✞🐘✞
I can take any political views, even contradictory, when it suits me. I.e. if Trump pays me a million USD to promote racism, I will be promoting racism, and if Hilary pays me million USD to speak against racism, I will be speaking against racism. For now I just hope that Americans will start killing each other in a civil war, so America will become less full and I could immigrate there. America actually needs a bloodshed. I.e. today I support both sides of the conflict, cheering for every American death. My argument is: pay me money and I will follow the party line. Otherwise I will be false flagging from the both sides, writing nasty things. Nostrovia! So I'm not right wing, I'm not left wing. I just hate Americans.
But no one gives any credence to someone with fluid and contradictory stances, so your false-flagging won't be anywhere near as efficient as it might be if you had credibility. That means that you are destroying the efficiency of your chosen tool, regardless of whether that tool choice makes any sense to begin with.
Not everyone is as smart as you. We are talking about the complete drooling American right wingers. These creatures have less intelligence than a retarded hamster. So why bothering puting in any effort, if most alt-rights get triggered?
Like in C++, destructor (dtor method) is called on variables when they leave scope. There is one exception. If the class has no copy constructor defined, then its dtor wont be called before return, and the object will be copied as is (byte-by-byte): CLst foo() { CLst xs; return xs; //if CLst has CLst.ctor_CLst method, it will be called //to make a copy, and the original object will get dtor'ed. //otherwise no dtor/ctor will be called, and xs itself //will be returned } rationale: it is more intuitive and useful default behavior.
Name:
Anonymous2021-04-12 14:16
Bit-level access to numbers please
Name:
Anonymous2021-04-12 14:44
>>35 C++ won't let you access int a=60343;a[1] //(1st bit) It has to be enum/class/struct.