Highlighted
Absent Member.
Absent Member.
1424 views

Native COBOL and OO support

Jump to solution

[Migrated content. Thread originally posted on 20 January 2011]

Can someone detail the emphasis being placed on support for OO COBOL in native environments? (ie. Win32, Unix).

I would really like to embrace the OO support but have a couple of major concerns:

1. OO documentation seems to almost be an 'addendum' in R2 release

In earlier product releases OO support was documented in its own manual with some examples and reasonable explanations of the functionality. That manual has disappeared and been replaced with pretty thin docs in R2. Haven't yet looked at R3.


2. Is this going to be enhanced in the same way as we are seeing for the .Net environment?

At the moment the native syntax is extremely verbose and nowhere near as evolved as what was demonstrated earlier today.

Are there plans in place to bring some of this functionality down to the non-.Net environments?


Thanks
0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.
Absent Member.

RE: Native COBOL and OO support

Jump to solution
Hi Greg,

1. Documentation is an area where we know we've got work to do. The OO syntax is being rolled into the mainstream documentation but it is still not as complete as we'd like it. In reality, I think a lot of people are really looking for good tutorials and demonstrations rather than abstract syntax charts and our intent is to use this Community to collect and publish a lot of that kind of material.

2. Our focus is on making COBOL as natural as possible for the .NET and JVM frameworks which, by their nature, are OO oriented. Although the Micro Focus Class Library was pretty useful, it's nowhere near as functionally rich or high-performing as those provided by .NET or JVM. Our focus will be on making those Class Libraries easier to use within in COBOL and to "smooth out" the variations between the different platforms. Some of this has started to appear in R3, for example the "string" class and "&" operator but there's a lot more we can do in this area.

If you haven't got it yet, I recommend you get a trial copy of R3 and start experimenting with the new syntax.

View solution in original post

0 Likes
1 Reply
Highlighted
Absent Member.
Absent Member.

RE: Native COBOL and OO support

Jump to solution
Hi Greg,

1. Documentation is an area where we know we've got work to do. The OO syntax is being rolled into the mainstream documentation but it is still not as complete as we'd like it. In reality, I think a lot of people are really looking for good tutorials and demonstrations rather than abstract syntax charts and our intent is to use this Community to collect and publish a lot of that kind of material.

2. Our focus is on making COBOL as natural as possible for the .NET and JVM frameworks which, by their nature, are OO oriented. Although the Micro Focus Class Library was pretty useful, it's nowhere near as functionally rich or high-performing as those provided by .NET or JVM. Our focus will be on making those Class Libraries easier to use within in COBOL and to "smooth out" the variations between the different platforms. Some of this has started to appear in R3, for example the "string" class and "&" operator but there's a lot more we can do in this area.

If you haven't got it yet, I recommend you get a trial copy of R3 and start experimenting with the new syntax.

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.