|
jhwurmbach wrote: His variable named "giraffe" was left in the code as to commemorate this guy.
And if there was a variable named 'dinosaur', that module can be declared obsolete too. Sometime back we had an interesting discussion on Dinosaur and VB in Soapbox. Perhaps if you are interested, check out this permalink:
http://www.codeproject.com/script/Forums/View.aspx?fid=2605&msg=2377913[^]
Vasudevan Deepak Kumar
Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson
|
|
|
|
|
Well, thats a step up from most Fortran code you see, which usually uses single letter variables - two letters if you're lucky.  /
|
|
|
|
|
We've got a ReleaseAnalWnd function kicking about in our codebase.
I've no idea if it was originally intentional or not as it's been sitting about since the dawn of the windows version of the software.
|
|
|
|
|
|
Analysis should not be abbreviated  too easy to end up as part of suggestive combinations.
|
|
|
|
|
an (ex-)colleague of mine (a highly paid consultant  ) had to take over some of my code and found nothing better than to select a global variable and do a replace ALL with "this." as prefix... After that the entire text kinda had a blue-ish shine to it... 
He took the code for 1 or 2 weeks and I spent 3 days in cleaning it up... a little.
|
|
|
|
|
we had a young whipper snapper MIT graduate on a project years ago (mid 90's) who used to use the stupidest variable names ever. His favorite was "smack"
if smack {<br />
<br />
} else {<br />
<br />
}
And he reused the same variable names in all the different modules. So you never really knew which smack you were look at.
The worst was when he instantiated a object and he named it after the client. The only issue was that the module was licensed to that particular client and when we used it on the next project it was the first clients direct competition. These "clients" were book publishers so they owned everything and when they were reading through the source code and came across their biggest competitors name they sorta blew a gasket, so to speak!! 
|
|
|
|
|
When I was a lad, working in a COBOL shop, there was a test program which used the names of all the punch room girls as variables. I can't recall what it did but it had memorable lines like: MOVE MARY TO BED and PERFORM SEX UNTIL SATISFIED.
Dave Cross
|
|
|
|
|
Yesterday I had an opportunity to visit a regional supermarket. Indian CPians would be able to understand and appreciate 'Trinetra (now 'More for you')', which has opened a lot of new outlets now.
After shopping, when I went to checkout, the console showed an interesting error
"Operation Is Not Allowed When the Object Is Closed"
Vasudevan Deepak Kumar
Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson
|
|
|
|
|
Least they are using objects 
|
|
|
|
|
To where did they outsourse their development? 
|
|
|
|
|
India of course
WPF - Imagineers Wanted
Follow your nose using DoubleAnimationUsingPath
|
|
|
|
|
PIEBALDconsult wrote: To where did they outsourse their development?
America.
|
|
|
|
|
Sounds like the stuff we're working on.... except we havn't released it to stores yet 
|
|
|
|
|
I was surfing on SourceMaking WebSiteCommand Pattern[^] and thought to post a reply to one of their video...
I didnt put entered req email field and submitted...
Here is the response  ...
warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/quotes.com/httpdocs/mega/modules/node/node.module on line 521.
warning: implode() [function.implode]: Invalid arguments passed in /home/httpd/vhosts/quotes.com/httpdocs/mega/modules/node/node.module on line 525.
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 query: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE in /home/httpd/vhosts/quotes.com/httpdocs/mega/includes/database.mysql.inc on line 172.
E-mail field is required.
Invalid CAPTCHA token.
The answer you entered for the CAPTCHA was not correct.
Keep DotNetting!!
GeekFromIndia
|
|
|
|
|
They are just asking for SQL Injection attacks I guess? My guess is that someone forgot to set a development flag to false.
|
|
|
|
|
Validations like 'Required Field' should be done at browser itself and if not there should be some kind of validation before sending data to DB...
Keep DotNetting!!
GeekFromIndia
|
|
|
|
|
geekfromindia wrote: Validations like 'Required Field' should be done at browser itself
I agree and it amazes me that occasionally people ask how to validate from the database side 
"I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon
|
|
|
|
|
Uh, while validating in the browser is nice, don't you need to validate on the server if you want to avoid an attack? What is to stop someone from writing a script to send whatever they want to your server, or turning off JavaScript?
I could see the browser validation doing something helpful like highlighting the bad field, while the server validation returns something a bit less friendly, like the name of a real web browser.
|
|
|
|
|
Andrew P Holden wrote: don't you need to validate on the server if you want to avoid an attack?
Yes, to prevent injection attacks.
Andrew P Holden wrote: What is to stop someone from writing a script to send whatever they want to your server
Good point. Validation should be done on both ends.
"I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon
|
|
|
|
|
Almost there.
Try verifying at the client - the input is of the right type - and then validating at the server. Validation is a business function ad so belongs away from the user interface.
Panic, Chaos, Destruction.
My work here is done.
|
|
|
|
|
williamnw wrote: Validation is a business function
Yes.
"I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon
|
|
|
|
|
Actually, this is great example why you need to place "php_value error_reporting 0" onto your production sites even if you completelly sure that your last code is right
By the way, if you interested, this site is build on Drupal CMS.
(those ugly errors were by my fault, Drupal is not guilty
|
|
|
|
|
I would think so 
"I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon
|
|
|
|
|
neochief wrote: Drupal is not guilty
Is that like saying Rupaul is not guilty? -- LOL
Silence is the voice of complicity.
Strange women lying in ponds distributing swords is no basis for a system of government. -- monty python
Might I suggest that the universe was always the size of the cosmos. It is just that at one point the cosmos was the size of a marble. -- Colin Angus Mackay
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
