|
Mladen Jankovic wrote: It's very useful debugging technique, especially in loops, although you can use "Breakpoint Conditions" for that matter:
sometime I insert quick and crappy code for debugging purposes. But always I comment that portion as being a debug code and not to be included in production. I insert the comment in case I forgot to remove the code and some one may catch it.
Most of the time I use break point conditions 
/* I can C */
// or !C
Yusuf
|
|
|
|
|
maybe too much:
drinkType == Whiskey
|
|
|
|
|
this could only be better with getter/setter methods!!
tbDrinkType.Text
{
get
{
return drinkType;
}
set
{
drinkType = value;
}
}
|
|
|
|
|
Management material. Why?
1. discussing what management likes to discuss most, drinking
2. In the way management communicats: repetition and redundancy
3. In the way management thinks: nonsensical
Marc
|
|
|
|
|
Can you explain the horror? At first I thought you were getting a value from a text box and putting it right back into the text box, but after closer inspection I see that isn't the case (assuming the language is case-sensitive).
|
|
|
|
|
David St. Hilaire wrote: Can you explain the horror? At first I thought you were getting a value from a text box and putting it right back into the text box, but after closer inspection I see that isn't the case (assuming the language is case-sensitive).
then what else is the code doing. The only exception is when the text in the TextBox is empty
Yusuf
|
|
|
|
|
The person who wrote this is simply checking if the text in the textbox is empty.
a simple:
<br />
if (tbDrinkType.Text == "")<br />
{<br />
}<br />
would have been quite satisfactory. 
|
|
|
|
|
I worked for a company once where we were developing a website where the powers that be wanted the site to be ultra secure. For whatever reason, they decided to go with a secuirty option offered by a company I'll just call SecuriCorp. SecuriCorp specialized in using a dongle with your website to authenticate. There are no user names, no passwords. I wasn't on the project, but heard all about it since it was the biggest project in the company. Each dongle had hardware set 6 digit keys and every time you pressed a button the next key would come up. The software knew what keys each dongle had and in what order they would appear. Once you logged in with a key, you couldn't use that key or any of the other keys on that dongle (thus eliminating dongle sharing). It seemed like a great idea, until one of the software architects for the project started to look in to how SecriCorp's security model worked. (Coincidentally, this architect was dubbed the "Dongle Doctor")
Their ultra security was setting a plaintext cookie named "Auth" with the value "true" Needless to say, the s$%# hit the fan. From that day on, any time on any project if you talked about security, someone would say "Just set Auth to true." When I left the company shortly after that, they were still in the midst of fighting with SecuriCorp to fix their "security" model.
Broken Bokken
http://www.brokenbokken.com
modified on Thursday, April 17, 2008 9:28 AM
|
|
|
|
|
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
|
|
|
|
|
|
The dongle thing is a standard security system. It was implemenred badly- implementation flaw.
|
|
|
|
|
I thought the idea of a dongle for the login was great, but you are right, it was a bad implementation. As a standard at that company, all our cookies were encrypted using Triple DES. It's just sad to see that much money put into a solution less secure than the one we already had working. 
Broken Bokken
You can't carry out a ninja-style assasination dressed as an astronaut. It's the luminous fabric; too visible. - Tripod
http://www.brokenbokken.com
|
|
|
|
|
|
|
Did you know VB.NET has a WriteOnly property to make properties into /dev/nulls?  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. 
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.
|
|
|
|
|
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  .
|
|
|
|
|
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.
|
|
|
|
|
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!
|
|
|
|
|
Yes, it's a good language, but I prefer C#.
Besides, WriteOnly is so weirdly funny! 
CLR: Removes tough Java-based stains fast!
|
|
|
|
|
Full ACK. It's those little advantages of C# like anonymous delegates, lambda expressions without return value, automatic properties, a.s.o. that made me prefer C#.
But one can't say VB is horrible! Basically, it has all features of C# and just an other syntax.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
