The syntax is similar to C++.
The .Net framework development languages are C# and VB.net. These both languages syntaxes were incorporated into the same framework to aclimatize programmers of both fields.
The syntax is similar to C++.
The .Net framework development languages are C# and VB.net. These both languages syntaxes were incorporated into the same framework to aclimatize programmers of both fields.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
And now we've got C++/CLI too!The .Net framework development languages are C# and VB.net. These both languages syntaxes were incorporated into the same framework to aclimatize programmers of both fields.
"Think not but that I know these things; or think
I know them not: not therefore am I short
Of knowing what I ought."
-John Milton, Paradise Regained (1671)
"Work hard and it might happen."
-XSquared
C++/CLI is not that evil. I mean... what do I care what Microsoft does to their .Net Framework if I don't plan to use it?
It is obviously the fact they may in the future enforce .Net on us and break any ties to ISO C++, that worries me.
But as long as I'm able to code for windows using ISO C++ and they keep an open interface to the system and the windows API, I can't care any less what .Net Framework does or stops doing.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
>The syntax is similar to C++.
The syntax is almost identical to Java (are we still talking about C#? This thread is so full of vomit technologies I can't keep track )
C# and C++Originally Posted by Perspective
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
Not that i'm real knowledgable when it comes to language agnostic, but here's my two cents.
No, CLI isn't standard. No, it doesn't run well (or at all) on other platforms. It does however, run well on Windows. Like CLI or not, if this is what MS decides to push on Windows developers, then that's how it may eventually have to be done (though there's a chance it won't, depending on what MS decides to do with .NET when Vista is released).
I happen to like CLI. I get the speed of C++ (arguably, as opposed to C#, which is arguable slower), and i'm able to use .NET. If you have no use for .NET, then you quite simple don't have any use for CLI, since .NET is really the only reason why we have CLI.
[/uneducated commentary]
[EDIT]
As far as the boards go, I'd say just keep the CLI stuff in the Windows forum, since, as I said above, CLI is really all about .NET (which is a Windows platform).
I don't see why C# can't have a forum though. It's entirely its own language, Java rip or not.
Last edited by psychopath; 07-11-2006 at 08:38 PM. Reason: To actually answer the main question.
M.Eng Computer Engineering CandidateB.Sc Computer Science
Robotics and graphics enthusiast.
We are not debating that fact. We are debating the fact that we are a C/C++ board and not just a computer language board.I don't see why C# can't have a forum though. It's entirely its own language, Java rip or not.
C# is not C/C++
Java is not C/C++
VB is not C/C++
CLI is not C/C++
I don't see the issue here. Seems fairly straightforward to me.
DirectX is not a language
OpenGL is not a language
MFC is not a language
ATL is not a language
Therefore, comparing a C# forum or CLI to MFC is like comparing apples to oranges. If you look closely at CLI, it's elements are quite simply....a new language.
Look at MFC, DirectX, OpenGL, etc,. They are in no way shape or form a completely new language. They do not add keywords to classes to gain functionality and they do not add to the core C/C++ language to gain any type of functionality.
Last edited by VirtualAce; 07-12-2006 at 12:11 AM.
I find the language name itself somewhat humorous:Originally Posted by Mario F.You'd think Microsoft, this big company with such far-reaching vision, would realize that the # character might not be the best thing to use?Originally Posted by WikipediaOriginally Posted by Microsoft
abachler: "A great programmer never stops optimizing a piece of code until it consists of nothing but preprocessor directives and comments "
I always want to call it C hash because for some reason, that's what # is supposed to be. I only think of it as sharp in music, which is almost never as I don't play an instrument. So I don't talk about it--if I make that mistake in reading, I'm bound to make it when speaking to someone.
It might be fugly or a considerable amount of work, but I like the idea of making CLI and C# subfora of Windows Programming, and move it up on the list along with Linux Programming. In a perfect world, this would work but I don't think that new people will spend time trying to find the CLI forum, at least that's what I was trying to figure out when I read this thread. While I still think some redesign would be nice, I think Prelude had the most reasonable idea.
I think of it as "C hash" too, because I'm known the twinkle the ivories and thus C sharp already has a meaning to me (It's the little black key to the right of C). For MS to camp on top of that is in my opinion stupid marketing. "C hash" accurately describes C# and has no other meaning (beyond narcotic connotations...).
Coverage of CLI may be mandatory for the Windows forum in the future, but I don't think we'll see a sufficient volume of posts to warrant its own forum for the time being, plus it'll never catch on for other platforms.
I perceive things like C# and Java to be on a different "level" to C/C++. Because they don't have true, dangerous AAAAGGGHHHH pointers and other things that you can shoot yourself in the foot with (to mention an oft-used quote ) they're higher-level languages to me and perhaps not suitable for discussion here.
I think the C# forum should be renamed "Other Programming Lanugages" where we can welcome C#, Java, Python, Lisp, assembly, etc... questions. The members of this board have a lot of helpful skills in other programming areas that are withheld by the lack of a good community outlet (such as the cboard) to display them. Other boards just don't have the same quality, or are just too flooded to be usable. Many posters here are students that have to use languages other than C/C++ and I'm sure they would welcome a place to post up those questions on the cboard. I for one, would be happy to help answer questions about java, python, lisp, etc...
I am in support of the other programming languages section too. I could answer questions for PHP Perl SQL and basics of Java.
I've never dabbled in C#; I always thought someone was trying to be cute: C++ is named from the increment operator applied to C, and this new language was an extension of C++ (or so I thought). So to apply the same naming logic, the name should be (C++)++. Then they just smashed the pluses together to make a sharp so that no one had to say C plus plus plus plus. Maybe I should stop daydreaming in the programming section of the bookstore.
There is a difference between tedious and difficult.
Personally I would prefer those languages to have no forum, too. But I actually see a C++/CLI forum as more justified than a C# forum.Originally Posted by Prelude
I agree with the "Other Programming Languages" forum, but I'd call it "C-like programming languages" and only permit languages with a C-like syntax
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law