[Cobolforgcc-devel] RE: [open-cobol-list] INITIALIZE Question
Status: Pre-Alpha
Brought to you by:
timjosling
From: Bill K. <wm...@ix...> - 2005-06-03 00:11:43
|
Maybe I am missing something, but I think this is "just a bug" in = OpenCOBOL. I believe the original INITIALIZE was a valid (ANSI/ISO conforming) use = of the statement with a DEFINED behavior - that OpenCOBOL is simply NOT = doing. (I haven't tried this myself to verify the reported results). When it comes to "undefined" or "extension" behavior, then you get into "which do you want". However, INITIALIZE of a GROUP-ITEM *must* = initialize all non-FILLER items of "standard defined" (i.e. not POINTER) USAGES. > -----Original Message----- > From: ope...@li...=20 > [mailto:ope...@li...] On=20 > Behalf Of Alain Lucari > Sent: Thursday, June 02, 2005 5:24 PM > To: ope...@li... > Subject: Re: [open-cobol-list] INITIALIZE Question >=20 > Hi all, >=20 > In my idea, the error is to think that=20 > you can have ONE cobol compiler wich do > the same that many others. >=20 > If you change your compiler from *M*F* to > *Acu* or *Acu* to *M*F* or others > YOU CAN CHANGE SOMETINGS IN YOURS CODE >=20 > Keisuke is very good (many guys have tried=20 > to made a cobol compiler but nobody have a > a good result) but I think that it is not possible > to emulate all the cobol compilers in one > or, at less too much difficult. >=20 > So, if you would use Open-Cobol, do the > same thing that you must do if you change, > "with some money", from a "commercial" compiler for an other : > test your code and do what is necessary. >=20 > Other thing : it is so easy with O-C to call > "system" that I don't undertand for what you are=20 > so excited about something like "intrinsic functions" > this is not easy with any commercial compiler. >=20 > Ok, it is good if this work (for how many peoples) > but if you destroy the compiler what is the benefit ?=20 >=20 > Le Thu, 2 Jun 2005 19:00:51 +0200 > Gue...@sm... a =E9crit: >=20 > >=20 > > Hello All, > >=20 > > I wonder if the INITIALIZE works correctly. > >=20 > > The output is different using mf instead of OpenCobol: > >=20 > > using mf (windows): > > MEM-LAST-I (1)=3D+0000 > > MEM-LAST-I (2)=3D+0000 > >=20 > > using OpenCobol: > > MEM-LAST-I (1)=3D+8224 > > MEM-LAST-I (2)=3D+0000 > >=20 > >=20 > > Kind regards > > Guenter >=20 > Best regards, > --=20 > Alain Lucari (Eurlix) >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > Search APIs Find out how you can build Yahoo! directly into your own > Applications - visit=20 > http://developer.yahoo.net/?fr=3Dfad-ysdn-ostg-q22005 > _______________________________________________ > open-cobol-list mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/open-cobol-list >=20 |