Comment On A Constant ... Constant?

Oh no, that guy is SOOO stupid; if he programs this way his app is not portable at all !

I mean, it doesn't even have a LF function to return the newline character when his app is gonna run on unix on a ported .net framework ...

What a n00b!

... erm, that is the wtf isn't it ?

guys?

*sound of crickets*

That is certainly ONE of them, in addition to the several which Alex mentioned in the intro post..

So where's the triumphant "see, something horrible in a language other than VB!"?  Guess they won't stoop to "our" level.  [:)]

:

You know, I just HAVE to say that I think a number of
regular posters here really need their sarcasm detectors repaired.



You DO have a sarcasm detector, don't you?

public static string CRLF = "/r/n";

to me that's a lot cleaner...

\r\n

Environment.NewLine is the way to go. Notice they didn't call it Environment.CRLF [:P]

I think this board needs a sarcasm emoticon. Way too many people get confused. Or perhaps we need a non-sarcasm emoticon and we just assume sarcasm by default.

brandonh6k:

Maybe I'm missing something here, but what about the vbCRLF constant?  Was that too obvious?

This is C#. vbCrLf is only in VB. Hence the "vb" prefix. [:P]

I suppose, however, he could have referenced Microsoft.VisualBasic.dll and used ControlChars.NewLine ...

Only thing worse would have been to make it a non static property.

Alex Papadimoulis:

brandonh6k wrote:

Maybe I'm missing something here, but what about the vbCRLF constant?  Was that too obvious?

This is C#. vbCrLf is only in VB. Hence the "vb" prefix.

I suppose, however, he could have referenced Microsoft.VisualBasic.dll and used ControlChars.NewLine ...

Well, duh... [:$] I guess my brain is in neutral today.  I looked at it earlier and my brain said VB...  Too much coding with not enough caffeine today.

seizethedave:

Initech eh? (office space)

Yea, I noticed that too. [8-|] Note the comment below the namespace

//namespace changed to protect the guilty

redtetrahedron:

seizethedave wrote:

Initech eh? (office space)

Yea, I noticed that too. Note the comment below the namespace

//namespace changed to protect the guilty

I'm a lazy reader.

:

public static string CRLF = "/r/n";

to me that's a lot cleaner...

Blue:

That is certainly ONE of them, in addition to the several which Alex mentioned in the intro post..

So where's the triumphant "see, something horrible in a language other than VB!"?  Guess they won't stoop to "our" level. 

 

 

Blue:

That is certainly ONE of them, in addition to the several which Alex mentioned in the intro post..

So where's the triumphant "see, something horrible in a language other than VB!"?  Guess they won't stoop to "our" level. 

 

 

Blue:

That is certainly ONE of them, in addition to the several which Alex mentioned in the intro post..

So where's the triumphant "see, something horrible in a language other than VB!"?  Guess they won't stoop to "our" level. 

 

 

Someone here mentioned vbCrLf... actually you can use that in C# (kinda), by referencing the Microsoft.VisualBasic assembly and then using Microsoft.VisualBasic.ControlChars.CrLf.

More to the point however, in all circumstances that I can think of, in C# a single \n will be seen as a line break. Unless you're writing a file in binary mode, you're not going to need \r\n. And even then there's the Environment.NewLine constant, which is automatically set to the correct character sequence for the platform.

foxyshadis:

This reminds me of XSLT; maybe the guy grew up there or in another language similarly restricted. XSLT's formatting is entirely implicit and generally implementation-defined - it works great for xml and html, when you don't care how the code looks, but it sucks for text out. So you have to define a newline to save yourself the burden of copy-pasting two long lines of code (!) every time, and whole functions just for each printf.

XSL is a lot like Java. It started out as a quickie language to fill a void - quick, easy, and simple translation of XML into other things by a few web developers - but it spiraled into a general purpose language. Not being designed for it, it sucks. (I happen to think it's fun and still the best way to access XML, but procedural languages are finally catching up, thankfully.)

If you're going to start dissing XSL, we'll need to go outside and have some words.

 Seriously, comparing XSL and Java? I've never heard of two things more different. The only thing they have in common is that ... because they... since they both... ummm...  they have absolutely nothing in common!

C'mon now. If it's not designed for something you need, don't use it! pfft.

:

Note that if someone's using "\r\n" they don't necessarily want
Environment.NetLine - they might require CR-LF for a protocol,
for example.

A message must...end with a 'carriage return - line feed' (CRLF)...

"Note that this is still .NET,  so it's nothing like C/C++. Seeing as there are more C# WTFs than C/C++ WTFs, I state that C# == VB."

Um... No.   I'd say this is clearly the work of a C programmer writing his first C# program.   Who else would cast an int to a char?

:

Have you tried Javascript? LOL

They're both turing complete.

JamesCurran:

"Note that this is still .NET,  so it's nothing like C/C++. Seeing as there are more C# WTFs than C/C++ WTFs, I state that C# == VB."

Um... No.   I'd say this is clearly the work of a C programmer writing his first C# program.   Who else would cast an int to a char?

 

Any C programmer that thinks assigning 10 or 13 to a char needs a cast, is not a C programmer.

[code language="c#"]

System.Environment.NewLine
[/code]

McGiv

He could use the stringbuilder to concatenate the strCR and strLF

BTW

"\r\n"

2 bytes, not 4 ;)

phx:

BTW

"\r\n"

2 bytes, not 4 ;)

Are you so sure those aren't Unicode characters?  [*-)]

Re: "This is the most pathetic thread of comments I've ever seen at this site.  What a great idea, Environment.NewLine() ??  or "\r\n"  ???   Brilliant!  Alex, you should have thought of these and mentioned them in your initial post! "

As opposed to the chock-full-o-content post you just made?

Oops, I just did it too! [:P]

phx:

BTW
"\r\n"
2 bytes, not 4 ;)

ahem....

First of all, "\r\n" is three bytes, not two (don't forget the terminating NUL)

Second, the joke was the the original poster had written "/r/n" which really is four (well, five) bytes. Scroll back and finally have the laugh that the rest of us had a week ago.

phx:

BTW

"\r\n"

2 bytes, not 4 ;)