|
Hm, I don't agree.
I wrote a C# program of more then 21.000 lines of code within 3 days. Which you probably won't write with C++ in 3 days (never tried, only used C++ for dos apps )
Anyway, everyone has a favorite. Your free to have that opinion, although I won't share it
C# is for me the best there is when it comes to possibilities. And the language looks like C++, so that's a positive thing, no need to learn a complete new way of writing code (syntax and stuff). Ok, some things are different but these are easy to learn.
Greetings....
|
|
|
|
|
So lets say you work 14 hours a day, you have coded? 500 lines per hour..
sounds not very real it you talking about brand new code.
seems to be a wizard created form app with many generated code to me.
But anyway.
we will see
|
|
|
|
|
"C# program of more then 21.000 lines of code within 3 days. Which you probably won't write with C++ in 3 days"
This would make c# a good prototyping language.
You can also write code in VB much faster than c++, but that doen't mean VB is a better language.
From you're own personal point of view you are tying you skills to a limited environment: Windows and .NET.
With c++ you can do anything on any platform, even mobile phones and emebedded devices.
|
|
|
|
|
Yeah i agree with you, c++/c programmer can move around from one platform to another which is good from the software company's point view. With C# you are stuck at one place and dont know what ur future will be if the company does not have any C# projects.
esdessdfsdfsd
|
|
|
|
|
An overly complicated version of C++? What exactly to you think C++ is?
int main(int ac, char** av)
{
std::cout << "Hello world" << std::endl;
}
C# comes nowhere near C++ in complexity. The only area where I find C# to be more rich of details is the runtime (.NET).
Judging by you statement, you don't know either C++ or C#.
--
Yeah well, my daddy can beat up your daddy!
|
|
|
|
|
10 REM This is a proper comment
"Your village called - They're missing their idiot."
|
|
|
|
|
Au contraire.
C
C THIS IS A PROPER COMMENT
C and this is too
;
; this is a proper comment
;
Software Zen: delete this;
|
|
|
|
|
Or even
# This is a comment
|
|
|
|
|
Lemme guess; Exormacs assembler for the 68000, right?
Software Zen: delete this;
|
|
|
|
|
'nuff said.
#endif
I think it's cool that Shog's coding johnson is longer than everyone elses
-- JoeSox 10/8/03
|
|
|
|
|
#if 0 is great for commenting out blocks of code that almost work, but not quite, so you can't use them.
If your nose runs and your feet smell, then you're built upside down.
|
|
|
|
|
What is XML comment way in C#?
Mazy
No sig. available now.
|
|
|
|
|
Example:
<summary> Some summary text to describe the member. </summary>
|
|
|
|
|
|
|
when u create the doc file, it's not much great to look at. Any idea where I could get hold of good xslt transforms that would present the whole thing in a good manner?
Rakesh
|
|
|
|
|
You're right. It's just XML after all. And the feature in Visual Studio to generate documentation web pages leaves a lot to be desired. However, there is one free tool in particular that makes XML commenting well worth it.
It's called NDoc[^]. From the site:
NDoc generates class libraries documentation from .NET assemblies and the XML documentation files generated by the C# compiler (or an add-on tool for VB.NET).
NDoc uses add-on documenters to generate documentation in several different formats, including the MSDN-style HTML Help format (.chm), the Visual Studio .NET Help format (HTML Help 2), and MSDN-online style web pages.
The NDoc source code is freely available under a certified Open Source license.
I recommend you take a look. It saved a lot of time when I was working on a rather LARGE project with many different components and APIs that the other developers had to know.
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
|
|
|
|
|
NDoc is real nice, used it to document some libraries I wrote for other people
Greetings....
|
|
|
|
|
Have you tried the "Build comment web pages" on the "Tools" menu?
|
|
|
|
|
Man...I never saw it before...thanks a lot!
|
|
|
|
|
Check out Doc-O-Matic. It'll handle comments in XMLDoc, JavaDoc, C, Delphi and other formats and produces nice looking documentation.
|
|
|
|
|
Seriously, #3 shouldn't be an issue since everyone should be commenting their code! I mean, throwing some one-time use script or app together is one thing, but if you're doing anything that you or others must maintain in the future, comments are a necessity! I know some people subscribe to the "my code is self-describing" idea, or even the "the code should be enough" idea, but how many people - especially in this day and age of "earn more money! get a job in computers!" code monkeys?
As far as code being "self-describing", the only code I've seen do that has variable names 20 characters or more long! Who wants to type that and waste line space for a stupid var?
For the "the code should be could enough" myth, peope like that forget that everyone has their own way of doing things (especially when it comes to coding styles). It may be good enough for you, but someone may be left scratching their head over why you did it that way. Even veteran programmers find it nice to read a comment (as grammatically incorrect as too many developers are these days) than several lines of code. It's easier to get an idea of the code that way. That's especially handy when you're trying to track down a bug in legacy source code.
Where I work, I'm one of the few people who comments code (mostly using the C# documentation syntax, as well as internal documentation). I force my developers to do so, too. The Industrial Engineers, however, (who are entry-level at best) never write comments and are always hacking code in the most inefficient manner, if it's even the right code. The reason (besides sucking)? They can't remember what the methods do or that they already did it!
I used to maintain documentation for our whole suite (it's big!) using NDoc and my own CHM->Help2 conversion program, but it was pointless because they didn't comment their code (the majority of the front-end UI and SQL scripts) and they didn't bother to read it (so instead bugged me incesently about what "X" does instead of RTFD).
There's just no excuse for this. At least add documentation for classes, methods, properties, etc. If not in the C# doc syntax, then in doxygen syntax or whatever you use. Generating documentation from source these days is trivial so there's just no excuse for not doing that.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.21
GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++
-----END GEEK CODE BLOCK-----
|
|
|
|
|
I agree fully. I try to document my code as well as possible, and I think there will be people (including myself!! ) who will be very glad that I did. Will even I remember 5 years down the road why I did something a certain way?
|
|
|
|
|
Heath Stewart wrote:
since everyone should be commenting their code!
Stop trolling!
"Vierteile den, der sie Hure schimpft mit einem türkischen Säbel."
sighist | Agile Programming | doxygen
|
|
|
|
|
C........
<edit>
I don't mean C language !
I'm programming in C# and i voted for first option. IMHO xml comments rocks !
</edit>
|
|
|
|