WriteOnly
-
Did you know VB.NET has a WriteOnly property to make properties into /dev/nulls? :wtf: It even offers IntelliSense to remove the Get accessors!
CLR: Removes tough Java-based stains fast!
So?
-
Did you know VB.NET has a WriteOnly property to make properties into /dev/nulls? :wtf: It even offers IntelliSense to remove the Get accessors!
CLR: Removes tough Java-based stains fast!
Who would use it? A coding horror in VB. And if you use it, it turns your code into a coding horror. X|
CLR: Removes tough Java-based stains fast!
-
Who would use it? A coding horror in VB. And if you use it, it turns your code into a coding horror. X|
CLR: Removes tough Java-based stains fast!
Did you also know VB is straight up just an ugly language? VB itself is a coding horror.
Mark Brock Click here to view my blog
-
Who would use it? A coding horror in VB. And if you use it, it turns your code into a coding horror. X|
CLR: Removes tough Java-based stains fast!
Alpha Nerd wrote:
And if you use it, it turns your code into a coding horror.
Surely if you use it, you have a reason, and thus your code will not be a horror?
Pits fall into Chuck Norris.
-
Did you also know VB is straight up just an ugly language? VB itself is a coding horror.
Mark Brock Click here to view my blog
This is the type of comment that only can be written by someone that doesnt know the language. I work on c# but i worked on VB.Net a few years before. The two main diferences i noticed on the transition was that intelisence is a lot better on VB, and on vb i don't have to compile the code to see errors.
-
This is the type of comment that only can be written by someone that doesnt know the language. I work on c# but i worked on VB.Net a few years before. The two main diferences i noticed on the transition was that intelisence is a lot better on VB, and on vb i don't have to compile the code to see errors.
Hey - I never said that VB is not a functional language, merely that it is an ugly language. I find myself constantly missing the "{}"'s that make C based code so elegant to look at ;).
Mark Brock Click here to view my blog
-
Did you know VB.NET has a WriteOnly property to make properties into /dev/nulls? :wtf: It even offers IntelliSense to remove the Get accessors!
CLR: Removes tough Java-based stains fast!
-
This is the type of comment that only can be written by someone that doesnt know the language. I work on c# but i worked on VB.Net a few years before. The two main diferences i noticed on the transition was that intelisence is a lot better on VB, and on vb i don't have to compile the code to see errors.
Member 2411327 wrote:
and on vb i don't have to compile the code to see errors.
I don't know what that isn't an IDE option. It's good for smaller projects but will hammer the CPU and slow the IDE down significantly on larger projects.
You know, every time I tried to win a bar-bet about being able to count to 1000 using my fingers I always got punched out when I reached 4.... -- El Corazon
-
Did you know VB.NET has a WriteOnly property to make properties into /dev/nulls? :wtf: It even offers IntelliSense to remove the Get accessors!
CLR: Removes tough Java-based stains fast!
Uhh, no. WriteOnly only turns off the gettor of a property. A /dev/null is a completely different concept.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
Member 2411327 wrote:
and on vb i don't have to compile the code to see errors.
I don't know what that isn't an IDE option. It's good for smaller projects but will hammer the CPU and slow the IDE down significantly on larger projects.
You know, every time I tried to win a bar-bet about being able to count to 1000 using my fingers I always got punched out when I reached 4.... -- El Corazon
dan neely wrote:
It's good for smaller projects but will hammer the CPU and slow the IDE down significantly on larger projects.
Doesn't matter. Its impossible to make a large project in VB anyway: you'll go crazy from the language itself;P
"impossible" is just an opinion.
-
Uhh, no. WriteOnly only turns off the gettor of a property. A /dev/null is a completely different concept.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008Who would turn off the gettor of a property? It turns them into black holes, and a /dev/null is one too.
CLR: Removes tough Java-based stains fast!
-
dan neely wrote:
It's good for smaller projects but will hammer the CPU and slow the IDE down significantly on larger projects.
Doesn't matter. Its impossible to make a large project in VB anyway: you'll go crazy from the language itself;P
"impossible" is just an opinion.
Hi all of you that think VB are such a horrible language to use for coding. I’ve notice some of you think a large project can’t be done in VB. Well, I’ve got news for you. I work for a company that develops Point of Sale software for the last 14 years, and we are currently working on a new version for the Point of Sale that has at least 2 million lines of source code in it! It is a full client-server application and can be used on a single PC and up to thousands of computers all with a breeze. Programming some parts of the application in C and other languages, VB still is the most organised and understandable code there is. Call a project with more than 2 million lines of source code small? The project contains about 121 dll’s written in VB6 and about 67 dll’s written in VB.Net. Currently we are converting all the VB6 dll’s to VB.Net dll’s. After all, it is not the language that makes an application what it is, but the programmer’s ability to develop good and reliable code, regardless of the language. ;)
A programmer's life is good... or is it?? Ek dink nie so nie!
-
Who would turn off the gettor of a property? It turns them into black holes, and a /dev/null is one too.
CLR: Removes tough Java-based stains fast!
Someone writing software to control an unbuffered output device? If there's no buffer, you can't change anything that was written out, so the getter is utterly pointless.
You know, every time I tried to win a bar-bet about being able to count to 1000 using my fingers I always got punched out when I reached 4.... -- El Corazon
-
Who would turn off the gettor of a property? It turns them into black holes, and a /dev/null is one too.
CLR: Removes tough Java-based stains fast!
Alpha Nerd wrote:
It turns them into black holes, and a /dev/null is one too.
Not quite. It turns a property into something akin to a voting box. You put your vote in, and there's no way to get it out. The class the property is defined in gets to do whatever it needs to with the data that comes in. In a "blackhole" null device, there isn't any processing allowable on the bits that end up in there...
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
Alpha Nerd wrote:
It turns them into black holes, and a /dev/null is one too.
Not quite. It turns a property into something akin to a voting box. You put your vote in, and there's no way to get it out. The class the property is defined in gets to do whatever it needs to with the data that comes in. In a "blackhole" null device, there isn't any processing allowable on the bits that end up in there...
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008you're familiar with the software that runs in a black hole? I want you to write an article on this, that is assuming you can get it out of there.
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.
-
Alpha Nerd wrote:
And if you use it, it turns your code into a coding horror.
Surely if you use it, you have a reason, and thus your code will not be a horror?
Pits fall into Chuck Norris.
There is no reason for an excuse of using that thing.
CLR: Removes tough Java-based stains fast!
-
There is no reason for an excuse of using that thing.
CLR: Removes tough Java-based stains fast!
Maybe the property is part of a quantum computer and so write only to spare the possible life of a cat.
-
Maybe the property is part of a quantum computer and so write only to spare the possible life of a cat.
Robert Surtees wrote:
Maybe the property is part of a quantum computer and so write only to spare the possible life of a cat.
You would need 9 WriteOnly properties then. Remember; they have 9 lives! LOL. :laugh: (who would build a supercomputer in VB? the language is slightly crippled, but this WriteOnly thing gives a advantage over C# or the awful C++)
CLR: Removes tough Java-based stains fast!
-
Alpha Nerd wrote:
It turns them into black holes, and a /dev/null is one too.
Not quite. It turns a property into something akin to a voting box. You put your vote in, and there's no way to get it out. The class the property is defined in gets to do whatever it needs to with the data that comes in. In a "blackhole" null device, there isn't any processing allowable on the bits that end up in there...
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008Unless you do this:
Public WriteOnly Property example As Object Set(ByVal value As Object) ' Do Nothing Here, Process Nothing Here End Set End PropertyCLR: Removes tough Java-based stains fast!
-
But you do it manually. (and I think it complains.) CLR: Removes tough Java-based stains fast!
