Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

In most programs I use descriptive variables that make the code easier to debug and document.

The only exception to this is the project from hell. Some idiot in the marketing department decided to sell a product that hasn't been built in ten years.

They also wanted some changes in the software and the hardware. This is a piece of test equipment that has C and assembly code embedded into the EPROM's on several PC boards. There was nobody left at the company that knew anything about the product. The software wasn't documented at all and some of the source code was missing but we still had the object files. The hardware department also had a difficult time because the schematics didn't match the PC boards.

Everybody that had to work on this project thought it was a waste of time and money except upper management.

When the C code was compiled there was about two hundred warnings. I did locate some people that originally worked on the software and they said the warnings are normal and just ignore them. We found a lot of if statements like this:  if (x=b){do_something;}. There should be two equal signs in the if statement.

For the new changes to the program we started using variables like:
waste_of_time
time_waster
money_waster
crap
worthless
piece_of_shit
junk


In reply to Re: Favorite Descriptive Variable Name by JohnB
in thread Favorite Descriptive Variable Name by vroom

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (2)
As of 2024-06-22 11:56 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?
    erzuuli‥ 🛈The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.