Beginning programming question

Thanks for the tips, Don. FWIW, Fortran is what I learned in college. Actually, I took a course, but never really learned it, because we had exactly two computers on campus, both of which were IBM 360s. I think it was Tuesdays that I had to turn in my punch cards at the computer center. On Monday, I'd get my output -- which almost always had an error or two.

You could go a month or more getting one program to run right. That meant four tries. It's a wonder we learned anything then, huh?

C isn't an exactly subset of C++. It comes pretty close, and it comes closer yet if the C code in question is written with good style. Certainly if you say "All C++ compilers will happily compile C that is _well written_ to _modern coding standards_", then you'll be much closer to the mark.

Here's the story from the Stroustrop's mouth, with examples:

I remember those days. I took it again many years later and was able to use a compiler that ran on a PC.

...

I may have been one of the first computer hackers. I noticed a Doctoral candidate submit a stack of punch cards, two full boxes, to the computer operator for the IBM 360. I was punching up a large stack for my GPSS (general purpose simulation system) class. That person came back in only two hours!

Next day, I struck up a conversation and asked to see her header cards, I must have something wrong. Anyway, started using those mysterious codes and getting my runs back in two hours. I aced that class and was even recognized by the prof. as writing some of the best code he'd seen. Karl

Ed, that reminds me of my experience with Fortran. I was working for a serv= ice bureau in Portland, Oregon. I had taken a Fortran class at the communit= y college, so was given the task of converting IBM 1130 Fortran to IBM 360 = Fortran to run on a model 40 machine.=20

Huge difference in the versions and the way each handled the instructions. = The customer was using the programs to schedule the loading of logs into sh= ips for shipment to Asia. Had to load properly to keep from upsetting the s= hip's balance in the water.

Finally got the reports to satisfy the customer, but when the 360 would pri= nt a line on the printer, all the lights on the console would turn on for a= bout 3 seconds, then one line would print! The Model 40 ran DOS with three = partitions. All would stop while the line of print was assembled. What a PO= S! that Fortran was when it came to I-O.

We never took on another Fortran conversion and never had another customer = try to use it.

Paul

:) Perl is the most awesome "git-r-done" language, it gets a job done quickly, has facilities to do stuff robustly. I can still easily read my perl stuff from years ago.

By the way, I bought a book for my 9 year old son to teach him programming. It is called "Hello World!" and it uses Python.

So far, he seems to like it.

So, I need to learn Python too, any suggestions for a good Python book for programmers. Something that would not explain in depth what is an if statement, just would explain how to use one.

thanks

rvice bureau in Portland, Oregon. I had taken a Fortran class at the commun= ity college, so was given the task of converting IBM 1130 Fortran to IBM 36=

. The customer was using the programs to schedule the loading of logs into = ships for shipment to Asia. Had to load properly to keep from upsetting the= ship's balance in the water.

rint a line on the printer, all the lights on the console would turn on for= about 3 seconds, then one line would print! The Model 40 ran DOS with thre= e partitions. All would stop while the line of print was assembled. What a = POS! that Fortran was when it came to I-O.

r try to use it.

Seriously Paul? Three seconds to print a single line? There MUST have been something else wrong. I had Fortran programs generate boxes of scrap paper pretty damned quickly on a 360.

When I asked a neighbor's kid (three years old at the time) what her father did at work, she said, "I think he makes paper for me to draw on." Her dad was a programmer on 360s, and he brought home boxes of scrap.

Ed, is this about learning about programming? or wrangling computers?

In the Windows environment, for actual programming, ASM - for me, still. VBA (Visual Basic for Applications) capabilities and Visual BASIC programming. (macro language for all MS apps)

May I offer that learning CAD would provide more personal range of operation that programming skills do not provide.

Agreed.

Well, that was a LONG time ago. Certainly more than 40 years! Maybe it just= seemed like 3 seconds. I know no other programs performed that way.

Paper? Yes, I bought home boxes of paper, to. Gave away to friends and neig= hbors. Still was creating boxes of paper up into the 1990's. I still have s= ome very large program listings that I am proud of.

One is a 360 assembly program that used direct calls to DOS for IO function= s. I was trying to access the console typewriter and other devices. Another= program listing is for a Burroughs computer that let me edit and compile p= rograms and control the computer remotely from a terminal. All the other pr= ogrammers were still using punched cards. Now days, it's hard to figure out= how the programs worked and what the code is doing.

Paul.

He's headed for a PhD in economics, with a master's in math along the way. His responsibilities at work are evolving. But his interest now is in learning basic programming, with an eye to learning something useful for his work. He doesn't really know what he's going to do with it. He does NOT want to be a professional programmer, although knowing the basics probably will help him.

I think he's picking up some VBA in his work with Excel. I recommended it to him last summer, when he was beginning to require lots of macros to automate Excel processes.

He has little interest. He watched me fiddling with it for years, when I wrote the CAD/CAM columns for a couple of manufacturing magazines, and later, when Ashlar was my client.

Heh, heh....I wasn't devious enough to do things like that. At least, not then. d8-)

That whole experience turned me off about programming. It wasn't until I got my first Apple II+ and started programming in BASIC that I regained any interest.

Then I got a RS M100 laptop and really started to have fun. I wrote a merchandise-distribution program for my wife -- she was a fashion buyer for

But I had written it for the 80C85, using all of the commands, and they couldn't make head nor tail out of it. My wife continued to run it on the RS M100.

Google 'Python tutorial'.

Have Fun! Rich

A real programmer learns algorithms, translating those into workable code then becomes the task. Knuth's set of books on the art of computer programming is a rather dense start to learning different ways of doing things in the computer world, there are other books. Or he could take some elementary college level courses. It's too bad most of the thrust in training these days is on a specific language rather than general knowlege, I've translated the same basic concepts into a half-dozen or more different languages and assemblers. There's nothing as constant as change in the computer world, if you know the underlying structure you want to translate, picking up a language to do it is kind of minor. Right now, the hot stuff is .NET, Java, maybe Python for beginners, along with a lot of web-oriented stuff. 10 years from now it'll be a bunch of things totally different.

If dealing with a lot of data, learning database techniques can be a plus. You can only go so far with Excel and the like. SQL is the key here.

Stan

Quick programs, bigger than a little scripting, would favor Python and maybe APL (Aplus is an available free variant). If the programs start to get big, an IDE (integrated development environment) and a C or variant (C++) program language are suitable. If his applied math program is any good, it'll cover this decision, though; there'll be requirements.

Java and VB are owner-controlled, which scares me. I've done years of work and then had the underlying language changed or withdrawn.

I made my living programming fortran for some years, back in the 1970s. IBM fortran was pretty good, but was industrial-strength complex. (But simpler than PL/1, but that's a whole other story.) I/O can be pretty complex. I never understood fortran I/O until some years later when I took Assembly Language, and saw how the kernel I/O services really worked. Only then did it become apparent how the fortran I/O must work.

Your boss blew it. He should have found someone who really knew fortran and its dialects, especially IBM's. One community college course isn't nearly enough, and it's no surprise that you couldn't figure it out having had only that one entry-level course.

Joe Gwinn

While this is true, it's far too deep in the details to matter in the present discussions.

In a sense, and to overstate the case, it's a bit like saying that US English and UK English are not quite identical, so let's learn Chinese instead. (Only to later discover that Chinese has hundreds of dialects.)

The newer C and/or C/C++ compilers tend to be more rigorous about enforcing the rules of the language than in the 1970s, which means that perfectly functional old code is often rejected by new compilers. There is a big debate in the programming community on if this is a good thing or a bad thing. I'm in the just-fix-the-errors-and-get-on-with-it school, but if the old codebase is valuable and huge, people just disable the warnings. I think all modern compilers have a single switch to return to the laxity of yore.

Joe Gwinn

I haven't kept up with current books about Python (a long time ago I bought a CORBA-via-Python book, which turned out not useful, and an overly elementary Python book) and have used online refs since to deal with particular questions. However, I've seen both of the following books recommended in comp.lang.python : "Python Standard Library", Fredrik Lundh, and "Python Cookbook, Second Edition", Martelli/Ravenscroft/Ascher, . Both are a few years old now and I don't know if newer versions are out.

My thought is that it isn't worthwhile to get a book about Python syntax, which can be presented well enough online. However, the Standard Library book should be able to present background and framework information that online man pages often lack, while the Cookbook presents numerous segments of code for specific purposes, which may be useful examples for learning Python. The tables of contents of both books are available at those O'Reilly links, so you may be able to see if one or the other matches up with what you want.

Also the books "Dive Into Python" and "How To Think Like A Computer Scientist" are online somewhere, and mailing list may help.