|
But it will compile finally to the target machine native processor code
|
|
|
|
|
It's JIT compiled, which is an implementation detail of the VM, similar to javascript on a modern browser.
Furthermore, setting aside that, it still cannot manage memory without the CLI, even compiled to native code. It requires the virtual machine in order to do basic operations. That machine is not simply part of the run time library like C's heap stuff. It's garbage collected - a process.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
honey the codewitch wrote: it still cannot manage memory without the CLI
This, along with some other 'limitations', is a limitation of the runtime, not the language.
And in relation to compiling, there is nothing in the language that prevents it being compiled.
=
|
|
|
|
|
Well said. Good words.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
As OriginalGriff said the similarities between C and C# are pretty superficial. It's really just syntactical: braces for for blocks, semicolon statement separators, simple data types (int, char, float, etc.) and simple control statements (if, for, while, etc.), other things I can't think of right now.
C, C#, C++, Java, Go, Rust, Kotlin, others? All share much of this same basic syntax. It makes it somewhat simpler to learn or move between them.
My understanding is C# was Microsoft's answer to Java after losing it's court case against Oracle over the future of Java in the late 1990's.
|
|
|
|
|
As an old member here answered once...
Do not forget that my compiler compiled your compiler.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
A proper C compiler is implemented in C and compiles itself. 
|
|
|
|
|
Doesn't that hold for the great majority of languges/compilers since around 1970?
Usually you need to create a small bootstrap in some other language. I was told (so I have no URL to back it up) that Nick Wirth attempted to write a compiler for the very first, super simple core Pascal (1970) in Fortran, but gave up and reverted to assembler - I don't know for which machine. Once this was running, all following extensions to full Pascal was written in the simpler Pascal dialect, as is the common strategy for all language/compiler bootstrapping.
I guess that languages deviating a lot from the algorithmic style (such as APL, Prolog, SNOBOL, Lisp, ...) have compilers / interpreters written in other languages, at least for production work. (I would be sort of surprised if no APL programmer has written an APL interpreter in APL!) But for the algorithmic languages group, the great majority have compilers expressed in themselves. This, of course, does not prohibit compilers written in other languages - I guess one main reason for that is that the compiler developer knows C only.
I know of one case where no bootstrapping in another language was required: The compiler was written in itself. Its developer put the compiler source up on the document holder by his keyboard, and compiled each statement in his head, typing in the machine instructions he knew that the compiler would generate. Of course he knew - he had written the compiler! This was in 1974.
Admittedly, this was a rather simple language - abstraction level was lower than K&R C. Yet it illustrates the principle of writing a compiler in its own language.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
To the best of my knowledge, the Multics PL/1 compiler was pretty much entirely written in PL/1. Of course, so was the great majority of the Multics operating system, from which sprung that which was called UNIX (formerly UNICS, a play on the Multics name).
In other, older, systems, compilers were quite often written entirely in the assembler of the host/target machine. I remember poring through the source of a COBOL-68 compiler trying to find a solution to what I thought was a rather stupid bug in the parser. The entire compiler was written in assembler, and printed out the source was over a foot thick.
|
|
|
|
|
trønderen wrote: I know of one case where no bootstrapping in another language was required:
The Forth Language, at least as originally created, was written like that. It requires a stack and very little beyond that.
|
|
|
|
|
You can end any initializer list and enumeration with a comma, just as in C.
... = { 1, 2, 3, };
Dennis M. Ritchie (may God rest his soul in peace) wrote that he was always forgetting to include a comma at the end of a row, when editing/extending such a list, and therefore changed the underlying grammar so that the C compiler accepts a last comma.
40 years later and many derived languages, nobody dared to change this.
It would be interesting to check if this syntax still applies to "modern" languages like JavaScript, Rust etc.
|
|
|
|
|
I learned C# many years ago coming from a Delphi background.
I found C# not that different from Delphi if you substitute begin and end with { and }
After all they were both developed by the same person. (Anders Hejlsberg - Wikipedia[^])
|
|
|
|
|
C# also supports pointers, malloc/free as well.
The Roslyn compiler supports code-generators, IDE analyzers, etc. C# is a much more productive & powerful language for most tasks. C is like portable ASM and is great to make component libs in.
|
|
|
|
|
zezba9000 wrote: C# also supports pointers, malloc/free as well.
If those are significant elements in your C# programming, I think you should consider returning back to C++.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
No, I really should not.
As C# productivity far exceeds that of C++ IMO. And normally code like this is rare. The compiler speed, Roslyn code-generators and compiler reflection is far better than C++ which is of huge value in todays world. Even for game dev. Is C# perfect, no but neither is C++. I actually use C way more than C++.
|
|
|
|
|
lol, no. So many reasons for a hard no.
|
|
|
|
|
As I remember it, C was the new kid on the block when I got out of college, designed and developed for the new UNIX operating system being promulgated by the Bell Telephone Company. Unlike FORTRAN, COBOL, and PL/1, each line of code compiled into only a few assembler instructions. But it had it's shortcomings. Because of the lack of strong typing and need to use explicit pointers, it was also an error prone language. Programmers had to really understand the hardware and how to use pointers effectively.
Advances in language theory and the advent of visual interfaces, such as Vermont Views, Windows, and OS/2, C was enhanced with strong typing, creating C++, and the Windows Forms visual UI libraries were added by Microsoft, creating C#.
__________________
Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now.
© 2009, Rex Hammock
|
|
|
|
|
Member 16280786 wrote: how understanding C might help in mastering C#.
It isn't that simple.
If you can program a simple program in C then you can likely write the same one in C#. But the concepts to create viable enterprise systems are not language specific.
Member 16280786 wrote: C# shares many basic syntax elements with C, such as data types (int, char, float), control structures (if, for, while), and operators (+, -, *, /). How much does familiarity with these elements in C help when learning C#?
That question resolves around my first point. If you know those well from C then it has no impact in learning C#. If you don't know them then you would still need to learn them regardless of which language you learn.
Member 16280786 wrote: C provides manual memory management using malloc and free, whereas C# handles memory through garbage collection. How does this difference impact the way we write and optimize code in C# compared to C?
Quite a bit.
Member 16280786 wrote: While C heavily relies on pointers, C# abstracts memory management but still allows the use of pointers in an unsafe context. How relevant are C pointers when dealing with C# programming, especially in performance-critical applications?
Unmanaged code does not matter much in enterprise systems because it isn't used. Even when use cases exist they represent a very small percentage of the overall code base.
However the question is simplistic because for a beginning programmer the concept of 'pointing to' is not that easy of a concept to grasp and use. That is why linked lists are often an early topic in teaching.
And that concept still exists in C#.
Member 16280786 wrote: C# is inherently object-oriented, unlike C. For those coming from a C background, how challenging is it to grasp the object-oriented concepts in C#? How can C principles aid in understanding these concepts?
It is a significant problem. Structured programming and Object Oriented Programming requires different designs not just code.
C programmers that move to any OO language will often end up creating designs that reflect structured programming rather than OO. I suspect going from OO to structured is quite difficult as well.
As a well known example Microsoft's first released C++ library was obviously just a wrapper for their existing C libraries.
Member 16280786 wrote: C# through .NET Core aims to be platform-independent, much like C programs can be compiled on various platforms. What are the key differences in achieving platform independence between the two languages?
The question is simplistic. Substantially different platforms introduce substantial problems regardless of the language. This is especially true when existing applications were not designed from the beginning with the core concept that they would need to run on different systems.
Member 16280786 wrote: C is often used for system-level programming and embedded systems, while C# is popular for web applications, desktop applications, and game development using Unity. How do these different use cases affect the choice of language and the transition from C to C#?
That question is not sensical. The first part is self answering. I am not sure what the second part even means.
|
|
|
|
|
Has anyone noticed that when you get a vscode update, the release notes never call out the bugs that were fixed.
<snark>I bet it's because the list is so large that it would cause the release notes file to be larger than the max possible size...</snark>
<moresnark>How do they exppect us to be able to reliably develop our own buggy code if the tools they provide us are so buggy?</moresnark>
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
They expect us to be dazzled by the list of wonderful enhancements.
|
|
|
|
|
The latest whiz-bang is "text to speech".
Speak this MS - "I don't give a f*ck about text to speech.".
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Still better than the vast majority of "app store"-type release notes, which are invariably some variation of:
Release Notes: Bug fixes and performance improvements.
Sometimes with slightly more embellishment, but it usually translates to the same meaningless BS. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Or so short, because they didn't fix a damn thing.
If you can't find time to do it right the first time, how are you going to find time to do it again?
PartsBin an Electronics Part Organizer - Release Version 1.4.0 (Many new features) JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
Microsoft fix bugs? 
When did they start doing that?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: Microsoft fix bugs?
No need when you can just enhance over them.
User: "Microsoft, have you fixed the xyz bug?"
MS: "Did you see the list of 300 enhancements including new fonts and icons?"
User: "Oh, look at all the shiny."
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
