Switch Editions? Mark channel Not-Safe-For-Work? Are you the publisher? Claim or contact us about this channel. Viewing all articles. First Page Page 25 Page 26 Page 27 Page 28 Page Last Page. Browse latest View live.
It was my mistake not providing the code correctly. This is the code snippet Code: 05 Sales-Data-County occurs 10 times. I tried your cross-platform code from above Scanning was resumed at the next area "A" item, level-number, or the start of the next clause. A blank was assumed. Skipped to the next verb, period or procedure-name definition.
The characters were discarded. And the "local variables" code There is no "Visual" anything on the mainframe. And, this is my point. The "modernization" leaves its roots behind, as though it's the ugly deformed stepchild that's kept in the basement.
But there is so much legacy COBOL out there that it needs to be addressed and allowed to still exist. But once I tell them, "but there are no viable free compilers that I've found and you need to get into. Net or JVM to really get anything done," they would all just say, "oh, well, I don't have time to get into anything new. And if JVM or. I'm not aware of any open version of COBOL being involved with the standards committee either though.
So, the year-tenured developers have the option of doing things the way they have been doing things for years, or they can add in some of the new features of the language. The nice thing is that the new features can be adopted gradually if so desired. This approach allows those same folks to move to things like C and Java at their pace instead of being forced to wholesale jump into the deep end. Search This Blog. When I get asked this, my first impression is that the person asking feels all alone in their use of the language, almost ashamed, believe it or not.
They've done a good job promoting the fact that if you are using the new gadget then you must be missing out. My answer to them is always the same. COBOL is an ever advancing language and is as current and modern as anything else out in the market. COBOL is in use every day in literally thousands of companies. But the number is shrinking. And I believe it is because of this perception that "we must be all alone".
Well, I've got news for everyone COBOL is still alive and kicking. Yes, usage is down. The numbers will continue to shrink until reaching an equilibrium or point of balance. Nowadays, there are literally hundreds if not thousands of ways to create and deploy a business application.
I think a very scientific number will be "a bunch of them". Not as many as there were, but enough to be significant. Today thousands of software companies, banks, insurance companies, manufacturers, and credit card processing companies are spending millions of dollars on their COBOL applications.
And they will continue to do so. As for those of us who write COBOL applications and are trying to figure out what they should focus on for the future, my advice is simple: Learn a framework like. NET and become somewhat language independent. Learn as much as you can about how to leverage things like. Already a member? Close this window and log in. Join Us Close. Join Tek-Tips Forums! Join Us! By joining you are opting in to receive e-mail.
Promoting, selling, recruiting, coursework and thesis posting is forbidden. Students Click Here. If I try to compile it, there are errors.
I am wondering which compiler will compiles that source without errors. Maybe they should try a "hello world" first, see if that is not too difficult for them. These errors are likely caused by the code's having passed through a word processor sometine in the posing process. It liked to mess up my code in ways simular to the above.
Before using code obtained from any published source, on should ensure that it is formatted properly for COBOL. Many languages don't care, they ignore white space.
0コメント