VB/C# Tips/Tricks
-
that is a lot of questions. If you have a common idea and several implementations, then yes, I would prefer to explain the idea first then offer implementations; or, alternatively, when explaining without implementation is hard to do, explain it once in a given implementation, then append alternatives to the initial document (hence not as alternates). The latter will not really be appreciated by people not familiar with your primary language though. The alternative is to write more than one T&T, give them similar titles (which do mention the implementation language), and add a note making them link to each other. The disadvantage is they will get diverging alternates, comments, replies, etc. However, there is another, and IMO bigger issue. I expect tip/tricks to be simple and concise (no more than two screenfuls), so maybe what you really should do is write an article. More than two languages would require an article for sure. Nuances, I wouldn't put them in a T&T. And then, assuming an article with only two languages involved, I prefer to show the implementations side-by-side, that is what I do sometimes on my site (e.g. here[^]). BTW: I don't fully agree with your language comment; I could very well imagine an algorithmic T&T implemented both in C# and Java, when the standard classes, not the language syntax, force you to take a slightly different approach. I know, the audience might be limited. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
Luc Pattyn wrote:
I don't fully agree with your language comment; I could very well imagine an algorithmic T&T implemented both in C# and Java, when the standard classes, not the language syntax, force you to take a slightly different approach.
Do you mean this comment?:
AspDotNetDev wrote:
Especially since I doubt many people will take things beyond VB.NET and C# (e.g., C++, Java, and so on).
Just to be clear, I mean that I don't see people writing a bunch of alternates for languages other than C# and VB.NET when the primary tip/trick and alternate are VB.NET and C#. Supposing somebody did decide to write a Java version, it may very well differ wildly from the C#/VB.NET version, which is another reason I would confine that to an alternate rather than clutter up the main text to explain both implementations when a reader only wants to know about one language. FYI, I created a suggestion to recommend CP make a way to create alternate views for a tip/trick (e.g., different languages) in addition to the existing "alternates" that currently exist.
-
If it's just a matter of code translation, it goes into the original tip/trick. I think I have one or two like that.
".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
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Sometimes there are slight variations. For example, VB.NET has a "select case" statement that works slightly different than the C# "switch" statement, so the tip/trick that made use of that had to show differing techniques between each language. It probably seemed a bit long-winded to somebody only interested in one language, so I split it into a tip/trick and an alternate.
-
Luc Pattyn wrote:
I don't fully agree with your language comment; I could very well imagine an algorithmic T&T implemented both in C# and Java, when the standard classes, not the language syntax, force you to take a slightly different approach.
Do you mean this comment?:
AspDotNetDev wrote:
Especially since I doubt many people will take things beyond VB.NET and C# (e.g., C++, Java, and so on).
Just to be clear, I mean that I don't see people writing a bunch of alternates for languages other than C# and VB.NET when the primary tip/trick and alternate are VB.NET and C#. Supposing somebody did decide to write a Java version, it may very well differ wildly from the C#/VB.NET version, which is another reason I would confine that to an alternate rather than clutter up the main text to explain both implementations when a reader only wants to know about one language. FYI, I created a suggestion to recommend CP make a way to create alternate views for a tip/trick (e.g., different languages) in addition to the existing "alternates" that currently exist.
AspDotNetDev wrote:
I don't see people writing a bunch of alternates for languages other than C# and VB.NET when the primary tip/trick and alternate are VB.NET and C#
Not if the TT is language oriented; however what if the TT is algorithmic, then any language could fit.
AspDotNetDev wrote:
FYI, I created a suggestion
I did notice, and managed not to react to it... :-D However, if CP staff decides to put in some effort to accomodate you, I'd much rather see them spend the effort to the articles subsystem than the TT subsystem. As I said, in my view TTs ought to be short and simple. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
-
Luc Pattyn wrote:
I don't fully agree with your language comment; I could very well imagine an algorithmic T&T implemented both in C# and Java, when the standard classes, not the language syntax, force you to take a slightly different approach.
Do you mean this comment?:
AspDotNetDev wrote:
Especially since I doubt many people will take things beyond VB.NET and C# (e.g., C++, Java, and so on).
Just to be clear, I mean that I don't see people writing a bunch of alternates for languages other than C# and VB.NET when the primary tip/trick and alternate are VB.NET and C#. Supposing somebody did decide to write a Java version, it may very well differ wildly from the C#/VB.NET version, which is another reason I would confine that to an alternate rather than clutter up the main text to explain both implementations when a reader only wants to know about one language. FYI, I created a suggestion to recommend CP make a way to create alternate views for a tip/trick (e.g., different languages) in addition to the existing "alternates" that currently exist.
I'm with Luc on this one. Put both versions in the Tip/Trick. Make it an article.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
-
I'm with Luc on this one. Put both versions in the Tip/Trick. Make it an article.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
Almost a repost. :laugh:
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
-
that is a lot of questions. If you have a common idea and several implementations, then yes, I would prefer to explain the idea first then offer implementations; or, alternatively, when explaining without implementation is hard to do, explain it once in a given implementation, then append alternatives to the initial document (hence not as alternates). The latter will not really be appreciated by people not familiar with your primary language though. The alternative is to write more than one T&T, give them similar titles (which do mention the implementation language), and add a note making them link to each other. The disadvantage is they will get diverging alternates, comments, replies, etc. However, there is another, and IMO bigger issue. I expect tip/tricks to be simple and concise (no more than two screenfuls), so maybe what you really should do is write an article. More than two languages would require an article for sure. Nuances, I wouldn't put them in a T&T. And then, assuming an article with only two languages involved, I prefer to show the implementations side-by-side, that is what I do sometimes on my site (e.g. here[^]). BTW: I don't fully agree with your language comment; I could very well imagine an algorithmic T&T implemented both in C# and Java, when the standard classes, not the language syntax, force you to take a slightly different approach. I know, the audience might be limited. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
I looked at your example article and really liked the way you showed both C# and VB, plus allowing the reader to collapse either the C# or VB code is a GREAT idea. I'm new to VB.net and have never used any language like C#, so reading something where all the code is only in C# I have found does not help me at all. Your approach works very well. Thank you for presenting it here.
-
I looked at your example article and really liked the way you showed both C# and VB, plus allowing the reader to collapse either the C# or VB code is a GREAT idea. I'm new to VB.net and have never used any language like C#, so reading something where all the code is only in C# I have found does not help me at all. Your approach works very well. Thank you for presenting it here.
:rose:
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
-
Speaking as a user/recipient, not a poster: here's another vote for posting both C# and VB.NET. (If you posted the Java, too, I'd read it out of curiosity... never done Java (don't drink coffee, either ;) and that would be an easy / interesting way to be introduced to some.) Thanks, -- Doug
-
You asked for my opinion, so here it goes and damn the univoters :~ If you want to write your bit in just C#, great, but please do not flag it as VB. Even if "the technique works in both languages", sample code in C# is not very helpful to someone who is not familiar with it: you may as well write your code in Fortran, COBOL or 6510 Assembly. If something is flagged for both C# and VB, it is reasonable to expect that the article will be useful to someone who uses only one of those languages. If that is not the case, then only one of those tags should be used.
-
Can we have an RPG forum? :laugh:
-
I expect an alternate to be creative, i.e. to offer another concept, another view on things, and not the same idea implemented in a different language. If you consider different languages alternates, then most every T&T could get alternates added to it, to do the same thing in different languages (C#, C++, VB, Java, PHP, Perl, etc.) and real alternates would be hard to find. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
I see that already or the "alternate" is a link to someone else' work. Are there guidelines or rules of thumb posted here?
-
I see that already or the "alternate" is a link to someone else' work. Are there guidelines or rules of thumb posted here?
Most FAQs can be reached through the "Help!" menu. Code Project Tips & Tricks FAQ[^] may be of interest to you. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
-
Most FAQs can be reached through the "Help!" menu. Code Project Tips & Tricks FAQ[^] may be of interest to you. :)
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
Thank you sir, much appreciated.
