Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
conversion from COBOL to C# (See Sharp)?
- Thread starter Crox
- Start date
There is no reason to convert; COBOL programs run faster. It might be better to generate a file for the internet in COBOL and use some other language to display it on the internet. COBOL can write HTML files easily it is just text. If you do not like my post feel free to point out your opinion or my errors.
- Thread starter
- #3
A C# conversion from COBOL makes NO Sense. Because Fujitsu has a .NET COBOL compiler - the only place C# lives is in .NET - you can interoperate between C# and COBOL SEAMLESSLY - you can even inherit C# objects from COBOL and COBOL objects from C#. The whole conversion is a silly idea.
- Thread starter
- #6
Again..... pffff
people say there is a product.
A want to know where, what and how.
Just because I want to know it.
Never having the idea to convert. I know COBOL and not C#.
On the other hand I can imagine that there are C# knowers whom don't want to learn COBOL....
Helas nobody answered the question yet.....
Regards,
Crox
people say there is a product.
A want to know where, what and how.
Just because I want to know it.
Never having the idea to convert. I know COBOL and not C#.
On the other hand I can imagine that there are C# knowers whom don't want to learn COBOL....
Helas nobody answered the question yet.....
Regards,
Crox
- Thread starter
- #8
Suppose you don't know C# and you know there is a beautiful program that you can use and possibly modify .... if it was in COBOL.
Or the other way around.
Why study a new language if you can stay with your own and become an expert in your programming language instead of knowing a little of many languages.
That is only one of the reasons why people want to convert.
Big companies do that all the time. Some of them want to convert all their mainframe COBOL and PL/1 into JAVA.
One of the reasons that people do that is because it is very difficult to let newbees work in the 'old' environments.... They all want to work with Internet, Java, C#, etc. So it can be a management reason to do things like that.
There are many more reasons why people want to do those things.
I don't think that anyone should convert COBOL to anything.
No!
No!
No!
It would be better if some people make others understand that COBOL is a beautiful language which is perfect to learn and understand and it is very smart to know all about it because it means much and nice work for many years.
But this is no text for a COBOL forum, more something for the front-page of several newspapers!
It is the press to blame for the wrong ideas of the newbees.
But still I would like to know about the conversion tools.
Regards,
Crox
Or the other way around.
Why study a new language if you can stay with your own and become an expert in your programming language instead of knowing a little of many languages.
That is only one of the reasons why people want to convert.
Big companies do that all the time. Some of them want to convert all their mainframe COBOL and PL/1 into JAVA.
One of the reasons that people do that is because it is very difficult to let newbees work in the 'old' environments.... They all want to work with Internet, Java, C#, etc. So it can be a management reason to do things like that.
There are many more reasons why people want to do those things.
I don't think that anyone should convert COBOL to anything.
No!
No!
No!
It would be better if some people make others understand that COBOL is a beautiful language which is perfect to learn and understand and it is very smart to know all about it because it means much and nice work for many years.
But this is no text for a COBOL forum, more something for the front-page of several newspapers!
It is the press to blame for the wrong ideas of the newbees.
But still I would like to know about the conversion tools.
Regards,
Crox
Maybe we have a language issue here. Crox asked about conversion from COBOL to C# and I said - no reason, because the only environment C# lives in is .NET and COBOL can exist in that environment - so there's no reason for such a conversion.
One could better argue a conversion from COBOL to Python - where the environment may or may not be common. Even so, I think we do not yet understand the question.
One could better argue a conversion from COBOL to Python - where the environment may or may not be common. Even so, I think we do not yet understand the question.
asiavoices
Programmer
I agree... I started off using COBOL and now I'm a ColdFusion/Java Developer.
I have always felt that COBOL is a very under-rated language and not given its due.
Imagine, if they come up with specifications to create COBOL-based objects, applications, classes, API ... it would take off and leave the other languages in the dust.
Best,
Christopher
I have always felt that COBOL is a very under-rated language and not given its due.
Imagine, if they come up with specifications to create COBOL-based objects, applications, classes, API ... it would take off and leave the other languages in the dust.
Best,
Christopher
- Thread starter
- #13
- Status
Similar threads
- Locked
- Question