Found a picture, here’s one of a few places I used the spikes. Yes, they attempted to make bird house on top of them, and higher up there’s another row of spikes they did make a bird nest.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
What’s on your mind?
- Thread starter Gutwrench
- Start date
- Sort by reaction score
Found a picture, here’s one of a few places I used the spikes. Yes, they attempted to make bird house on top of them, and higher up there’s another row of spikes they did make a bird nest.
The style and documentation requirements can vary depending on the company you’re working for, the project you’re on, or even the instructor in your class. For instance, in my C++ class, my professor was super strict about grading. He would deduct points if you didn’t include multiline comments with your name, homework number, and the instructor’s name on your code. Even missing comments describing functions or classes could result in an automatic zero. I had to redo a lot of my homework because of all these requirements, including coding style. 😳
Were there any pigeons leaving droppings and building nests all over your property? If so, you should get your gutters cleaned, even the eaves of your home. It’s a lot of work to get these birds off your property.
Yes, I really enjoy them. They will be available in season until the end of spring. I love eating them all the time, wherever they are available! Have you tried Cara Cara oranges?
I applaud that instructor.
I'm betting that the majority of developers are sloppy and refuse to document their work. I worked with many like that in C and C++. I did everything I could so that the next person to pick up the work could be informed.
After I got a job programming in Fortran for a Fisheries Research organisation, this was one of my first purchases --
It was built around the concepts in "Elements of Style", which I also later bought.
Looking at the price, I am astonished that I spent AU$10 on this book, in 1980, when AU$1 was about US$2.
One of the things I used to do when I had to start programming a routine was to just write a paragraph or two in comments about what I wanted the routine to do, and how to go about it, in plain English. Then I would start coding. Because of this I was often able to get working code very quickly.
It was built around the concepts in "Elements of Style", which I also later bought.
Looking at the price, I am astonished that I spent AU$10 on this book, in 1980, when AU$1 was about US$2.
One of the things I used to do when I had to start programming a routine was to just write a paragraph or two in comments about what I wanted the routine to do, and how to go about it, in plain English. Then I would start coding. Because of this I was often able to get working code very quickly.
Comments started with a "*" in column 7, didn't they?
Every FORTRAN programme I read had a GOTO 999 to finish but that was in the days of spaghetti code.
Even in my JavaScript class with APCSP at my previous school, we were taught the basics and importance of comments from the very beginning. This preparation was crucial as we started working on our apps for the national Congressional App Challenge, which ultimately led to our capstone project.
I still had this picture in my photo library. 😂 However, I did still refer back to it with my C++, Java, and other programming classes that I’ve been taking recently. Even I use multi-line comments to label my programs for homework assignments, as some require the submission of a package or multiple files. 📄
That must have been before Fortran IV. According to this document any character except 0 in column 6 continues the line on from the previous one (because you only had 80 characters, and only 73 were available for code).
As well, all the programs I was familiar with simply had END as the last statement.
So long as the code got there. As with any language, there are innumerable ways of setting up an infinite loop which never exits. And if you weren't careful with the array you were setting up, you could gradually eat all the memory in the computer, resulting in throwing off 150+ current users, with all them then desiring to examine your entrails in great detail... The University of Sydney is still looking for the two miscreants.
It's been slightly over 40 years since I last coded any FORTRAN. Our editor had the fields broken up so that I could tell immediately where to put the character for a comment.
One of my co-workers in 1990 told me that the instructor of a certain class posed a ridiculous way to get an "A" in the class. He told the class if they could pop the lid on the printer in the computer lab, they had an automatic A.
He found a way to not transmit the carriage return, line feed combination and printed so many times on the same line that it caused the printer to overheat and pop the lid. It caused massive damage to the printer and the student got his "A" but the instructor was probably instructed about how much it would cost to repair or replace the printer.