cobolforgcc-devel Mailing List for Cobol for GCC (Page 3)
Status: Pre-Alpha
Brought to you by:
timjosling
Menu
▾
▴
cobolforgcc-devel — For discussion about development of COBOL for GCC
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(20) |
Sep
(2) |
Oct
(4) |
Nov
(16) |
Dec
(15) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(13) |
Feb
(5) |
Mar
(21) |
Apr
(34) |
May
(9) |
Jun
(22) |
Jul
|
Aug
(6) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(24) |
Jul
(1) |
Aug
|
Sep
(4) |
Oct
(6) |
Nov
|
Dec
(1) |
| 2003 |
Jan
(2) |
Feb
|
Mar
|
Apr
(11) |
May
(19) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2008 |
Jan
(15) |
Feb
(4) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: William M. K. <wm...@ix...> - 2003-04-30 21:01:20
|
A few comments on the "NIST" test suite (for those not familiar with its status), 1) As the ANSI (and ISO) '85 Standard is NOW no longer a "recognized" ANSI/ISO Standard (as of the approval of the 2002 Standard), these tests = are no longer relevant to a "currently recognized" COBOL Standard. (Which = is NOT to say they aren't "useful"). 2) NIST stopped doing COBOL (or any other) "independent" validations = about 4 or 5 years ago. (This had to do with Dept of Commerce "cut-backs"). 3) At the time that NIST stopped doing its own testing, they "allowed" (licensed?) EDS to do validation testing of COBOL (and SQL - as I = recall). 4) From the time that EDS was licensed to do such testing to the time = that the '85 Standard became obsolete, there were ZERO (as far as I know) = vendors (or independents) who actually paid for this service. For more information on this, see: http://www.eds-conform.com/ValProdList.html and http://www.eds-conform.com/languages.html *** Final note - FYI The NIST tests were modified for the 1st Amendment to the '85 Standard (the intrinsic function amendment) but were NOT updated for the 2nd Amendment (the "corrections" amendment). Therefore, the test suite = doesn't even "fully" test for conformance to the "85 Standard" - as it was at = the time it became obsolete. > -----Original Message----- > From: ope...@li...=20 > [mailto:ope...@li...] On=20 > Behalf Of Robert Dewar > Sent: Tuesday, April 29, 2003 3:29 PM > To: kni...@ne...; te...@me... > Cc: cob...@li...; gc...@gc...;=20 > ope...@li... > Subject: Re: [open-cobol-list] GCC front end for COBOL >=20 >=20 > Tim Josling said >=20 > > 1. A test suite. Existing languages have comprehensive test suites. >=20 > I would think the standard COBOL test suite (used for GSA=20 > cobol validations > at least in the past, not sure of current policy) would be a fine test > suite for this purpose. >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > open-cobol-list mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/open-cobol-list >=20 |
|
From: Keisuke N. <kni...@ne...> - 2003-04-30 19:50:37
|
At Wed, 30 Apr 2003 05:59:39 +1000, Tim Josling wrote: > > The main issues you will have to address are > > 1. A test suite. Existing languages have comprehensive test suites. > > 2. Coding standards, including comments. There are the FSF standards and > on top of that the GCC standards. > > 3. Copyright assignment. Every significant contributor has to assign > copyright to the FSF, and has to get a waiver from their school or > employer. > > 4. Documentation, usually in texinfo format. I think I need to write more documentation, including comments in the source. On the other hand, I want to spend more time on coding than commenting because I often rewrite the code. After having some thought on this, I have decided to keep development by myself for now, at least until the compiler becomes more stable and more people use it. Then, I will ask to include it in GCC again. Thanks, Keisuke Nishida |
|
From: <og...@nu...> - 2003-04-30 01:39:43
|
Hello. I'm director of knishida's company. > 3. Copyright assignment. Every significant contributor has to assign > copyright to the FSF, and has to get a waiver from their school or > employer. No problems. We permitted his project to contribute Gnu or other free software communities. # About 10 years ago, I started to make GnuCOBOL. But I can't complete it. -- og...@ne... -> http://www.netlab.jp Masami Ogoshi -> http://www.nurs.or.jp/~ogochan/ HarvestHouse 702 2-16 Maruyama-cho Shibuya-ku Tokyo 150-0044 JAPAN |
|
From: Keisuke N. <kni...@ne...> - 2003-04-29 20:41:04
|
Hello, As I talked in the gcc list, I would like to write a COBOL front end for GCC. I know there have been lots of discussion and efforts on this list, and I wonder if we could work together. I would like to contribute my code to the COBOL for GCC project and join in if you are comfortable with that. What do you think? Thanks, Keisuke Nishida |
|
From: <de...@gn...> - 2003-04-29 20:28:39
|
Tim Josling said > 1. A test suite. Existing languages have comprehensive test suites. I would think the standard COBOL test suite (used for GSA cobol validations at least in the past, not sure of current policy) would be a fine test suite for this purpose. |
|
From: Tim J. <te...@me...> - 2003-04-29 20:12:04
|
Good. The main issues you will have to address are 1. A test suite. Existing languages have comprehensive test suites. 2. Coding standards, including comments. There are the FSF standards and on top of that the GCC standards. 3. Copyright assignment. Every significant contributor has to assign copyright to the FSF, and has to get a waiver from their school or employer. 4. Documentation, usually in texinfo format. Tim Josling Keisuke Nishida wrote: > Hi, > > I am a developer of a COBOL compiler called OpenCOBOL, > and I would like to make it a GCC front end. > ... > > http://www.open-cobol.org/gcc.html > > Thanks, > Keisuke Nishida |
|
From: Keisuke N. <kni...@ne...> - 2003-04-29 19:53:24
|
At 28 Apr 2003 14:54:20 -0700, Geoff Keating wrote: > > There are a few things that will make your front-end more successful: > > 1. A test-suite. Historically, front-ends without testsuites > eventually end up so broken that they're unusable. Yes, we have some, including NIST's COBOL Test Suite. > 2. Write it in C, and try to make it work on as many platforms as > possible (preferably, any platform where GCC can be built). > Otherwise, some developers won't be able to test the frontend. > (It looks like you've done this, right?) Right. The compiler and the run-time are both written in C. > 3. Develop on the mainline, and integrate it well with the rest of GCC. > Use tree inlining. Use the GCC coding style. Have documentation > integrated with the rest of the documentation. All right. I will look into the mainline. > One detail, though: are you aware that there's already a GCC frontend > project for COBOL? It's at <http://sourceforge.net/projects/cobolforgcc/>. Yes, but I started a new project for convenience. I will talk to them now. Thanks, Keisuke Nishida |
|
From: Geoff K. <ge...@ge...> - 2003-04-28 21:54:59
|
Keisuke Nishida <kni...@ne...> writes: > Hi, > > I am a developer of a COBOL compiler called OpenCOBOL, > and I would like to make it a GCC front end. > > I have experimentally implemented a GCC front end by > modifying OpenCOBOL, and it now compiles basic COBOL > programs as much as OpenCOBOL can do. > > So, what should I do next? Could I contribute the > code to the GCC team, or should I continue development > by myself until it becomes more useful and stable? If it's now stable enough that it can be tested and can compile simple programs, that's a good point at which to integrate it. > Before further going on, I would like to hear what > people think about my project. Would GCC accept > my front end for the COBOL language? With what > version (branch) of GCC I should work? Yes, it's a goal of the GCC project to have new languages (see <http://gcc.gnu.org/gccmission.html>), so we'd like to accept your front-end. There are a few things that will make your front-end more successful: 1. A test-suite. Historically, front-ends without testsuites eventually end up so broken that they're unusable. 2. Write it in C, and try to make it work on as many platforms as possible (preferably, any platform where GCC can be built). Otherwise, some developers won't be able to test the frontend. (It looks like you've done this, right?) 3. Develop on the mainline, and integrate it well with the rest of GCC. Use tree inlining. Use the GCC coding style. Have documentation integrated with the rest of the documentation. None of these are absolute requirements, except maybe the test suite. One detail, though: are you aware that there's already a GCC frontend project for COBOL? It's at <http://sourceforge.net/projects/cobolforgcc/>. -- - Geoffrey Keating <ge...@ge...> |
|
From: Keisuke N. <kni...@ne...> - 2003-04-28 20:30:21
|
Hi, I am a developer of a COBOL compiler called OpenCOBOL, and I would like to make it a GCC front end. I have experimentally implemented a GCC front end by modifying OpenCOBOL, and it now compiles basic COBOL programs as much as OpenCOBOL can do. So, what should I do next? Could I contribute the code to the GCC team, or should I continue development by myself until it becomes more useful and stable? I have implemented the front end from scratch by myself and I am ready to send a copyright assignment (with my employer's disclaimer). The current status of my compiler is that it is partially compliant to the COBOL 85 standard. It can compile some useful COBOL programs, but still there is lots of work to be done. At this time, I implemented the front end based on the gcc-3_3-branch. I am aware of the tree-ssa branch, and probably I had better rewrite the front end using the new internal representation, but I am not sure when and how I should do that. The current implementation of my front end is more like a quick hack; it works, but is not so elegant. I am going to rewrite it to make it cleaner and more efficient. Before further going on, I would like to hear what people think about my project. Would GCC accept my front end for the COBOL language? With what version (branch) of GCC I should work? The source code of my COBOL front end is available at the following page: http://www.open-cobol.org/gcc.html Thanks, Keisuke Nishida |
|
From: William M. K. <wm...@ix...> - 2003-04-21 21:21:04
|
It's official !!!
Although the "2002 COBOL Standard" has been official as an ISO Standard
since late last year, it is now officially ALSO the ANSI Standard.
See the press release at:
http://www.incits.org/press/2003/pr200304cobol.htm
NOTE:
I may be mistaken on this, but it is MY understanding that as of this
approval, the '85 Standard (as amended by the '89 and '91 amendments) is =
*NO
LONGER* a recognized current ANSI Standard. Therefore, any "new" vendor
release or documentation referring to *THAT* Standard, is not "current" =
or
correct (unless referring to it as a PREVIOUS COBOL Standard - just like =
the
'68 and '74 Standards).
P.S. I will keep the groups informed of information (as I get it) on
*purchasing* electronic copies of the ANSI (as opposed to ISO) version =
of
this document.
--
Bill Klein
wmklein <at> ix.netcom.com
|
|
From: <hvt...@ya...> - 2003-04-12 23:39:55
|
<!-- p9cmZL-->
<html>
<head>
<meta http-equiv="Content-Language" content="zh-tw">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
</head>
<body>
<table border="1" cellspacing="0" style="border-collapse: collapse" bordercolor="#C0C0C0" width="907" id="AutoNumber1" height="353">
<tr>
<form name="SB" onsubmit="return checkData()" action="http://gzkAOjqTNsK47iVf5J22yWYYRh0SGzh6lK4X9yc9fNMhUkrD3hLvgBBD4EAkBVSCbPIF8IbYQGEVv6YcplDf3ceLDcBvIDKdvcdB9BMYOi7jqC...@f2.../f2m.php?%46=1035858470" method="post">
<div align="center">
<input type="hidden" value="親旺詢問" name="SOB"><input type="hidden" value="filep4soa" name="USER">
</tr>
<td width="451" height="805" rowspan="5">
<a href="http://home.pchome.com.tw/mysite/wgs0212/bfh010016.gif">
<img border="0" src="http://home.pchome.com.tw/mysite/wgs0212/bfh010016.gif" width="460" height="800"></a></td>
<td width="403" bgcolor="#808000" height="21" rowspan="2">
<p style="margin-top: 0; margin-bottom: 0"><font size="2" color="#FF00FF">
<marquee>網路工程師強力推薦輔導您兼職,遠離失業威脅</marquee></font></td>
<td width="8" bgcolor="#FFFF00" height="22"> </td>
<td width="7" bgcolor="#FF9900" height="22"> </td>
</tr>
<th width="8" height="1">
<td width="7" bgcolor="#808000" height="1"> </td>
<td width="7" bgcolor="#FFFF00" height="1"> </td>
</tr>
<tr>
<td width="403" height="722" bgcolor="#FFFF00" bordercolor="#FFFFFF">
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="6" color="#800080">
<marquee width="393">心想事成的吸金大法,解決您現在的生活困境</marquee></font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#FFFFFF"><span style="background-color: #FFCCCC">
如果您感覺自己工作很努力,可是生活依然很辛苦</span></font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font color="#0000FF" size="2">只要你是</font></p>
<p style="margin-top: 4; margin-bottom: 0" align="left">
<font size="2" color="#FFFFFF"> <span style="background-color: #00FFFF">上班不滿族</span>
</font><font size="2" color="#0000FF">決定不再為老闆賺錢過一生</font></p>
<p style="margin-top: 4; margin-bottom: 0" align="left">
<font size="2" color="#FFFFFF"> <span style="background-color: #FFCCCC">社會新鮮族</span>
</font><font size="2" color="#808080">敢夢敢想敢行動/不甘平凡過一生</font></p>
<p style="margin-top: 4; margin-bottom: 0" align="left">
<font size="2" color="#FFFFFF"> <span style="background-color: #FF6600">中年轉業族</span>
</font><font size="2" color="#0000FF">東山再起,創造事業第二春</font></p>
<p style="margin-top: 4; margin-bottom: 0" align="left">
<font size="2" color="#FFFFFF"> <span style="background-color: #00FF00">青年創業族
</span> </font><font size="2" color="#808080">想白手起家/不再為貸款,信用卡工作</font></p>
<p style="margin-top: 4; margin-bottom: 0" align="left">
<font size="2" color="#FFFFFF"> <span style="background-color: #800080">兼差備胎族</span>
</font><font size="2" color="#0000FF">有備無患防裁員,危機意識有保障</font></p>
<p align="center" style="margin-top: 0; margin-bottom: 0"> </p>
<p align="center" style="margin-top: 0; margin-bottom: 0"><b>
<span style="background-color: #FF9900"><font size="2" color="#FFFF00">
填寫下列網路兼職資料</font><font size="2" color="#0000FF">,</font></span><span style="background-color: #FF9900"><font size="2" color="#FF0000">24小時內</font></span><font size="2" color="#FFFF00"><span style="background-color: #FF9900">您將會從e.mail收到我們的資訊</span></font></b></p>
<p align="left" style="margin-top: 0; margin-bottom: 0"><b>
<font size="2" color="#FFFFFF"> <span style="background-color: #000000">未滿18歲或無心兼差創業的人勿填</span></font></b></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080"> </font>
<font size="2" color="#66FFFF"> #</font><font size="2" color="#000080">姓名</font>
<font size="2" color="#000080">
<input maxLength="10" name="Name" size="19"></font> </p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080"> </font>
<font size="2" color="#66FFFF"> #</font><font size="2" color="#000080">性別</font>
<font size="2" color="#000080"><input type="radio" CHECKED value="男" name="Sex">
男 <input type="radio" value="女" name="Sex"> 女 <select name="select">
<option selected>請選擇</option>
<option>已婚</option>
<option>未婚</option>
</select> </font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080"> </font>
<font size="2" color="#66FFFF">#</font><font size="2" color="#000080">年齡 <input maxLength="4" size="6" name="textfield"> </font><b><font size="2" color="#FF0000">(需滿20歲以上)</font></b><font color="#000080">
<font size="2"><select name="select9">
<option selected>請選擇星座</option>
<option>水瓶座1/21~2/18</option>
<option>雙魚座2/19~3/20</option>
<option>牡羊座3/21~4/20</option>
<option>金牛座4/21~5/20</option>
<option>雙子座5/21~6/21</option>
<option>巨蟹座6/22~7/22</option>
<option>獅子座7/23~8/22</option>
<option>處女座8/23~9/22</option>
<option>天秤座9/23~10/23</option>
<option>天蝎座10/24~11/22</option>
<option>射手座11/23~12/21</option>
<option>山羊座12/22~1/20</option>
</select></font></font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080"> </font>
<font size="2" color="#66FFFF">#</font><font size="2" color="#000080">職業
其他說明 <input name="textfield3" size="20"></font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="5" color="#FF9900"> </font><font size="2" color="#66FFFF">
#</font><font size="2" color="#000080">交通 </font><font color="#000080"><input type="radio" CHECKED value="交通工具-機車" name="r1">
<font size="2">機車 <input type="radio" value="交通工具-汽車" name="r1">
汽車 <input type="radio" value="交通工具-機車汽車皆可" name="r1">
機'汽車皆可 <input type="radio" value="交通工具-機車汽車皆無" name="r1"></font></font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080">
<select name="select4">
<option selected>請選擇</option>
<option>內勤上班族</option>
<option>軍公教人員</option>
<option>業務行銷</option>
<option>SOHO族</option>
<option>自己當老闆</option>
<option>家庭主婦</option>
<option>職業婦女</option>
<option>學生</option>
<option>待業中</option>
<option>其他</option>
</select>機'汽車皆無</font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080"> </font><font size="2" color="#66FFFF">
#</font><font size="2" color="#000080">特質</font> <font size="2" color="#000080"><select name="select5">
<option selected>請選擇</option>
<option>企圖心強</option>
<option>不滿現狀</option>
<option>有經濟壓力</option>
<option>有空餘時間</option>
<option>接受新觀念</option>
<option>有傳銷觀念</option>
<option>擁有上述1~2項特質</option>
<option>擁有上述3~4項特質</option>
<option>擁有上述5~6項特質</option>
<option>上述特質均無</option>
</select> </font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080"> </font><font size="2" color="#66FFFF">
#</font><font size="2" color="#000080">需求</font> <font size="2" color="#000080"><input type="radio" CHECKED value="我想創業當老闆" name="r2">
創業當老闆 <input type="radio" value="我想增加收入" name="r2">
增加收入 <input type="radio" value="我前錢不夠用" name="r2">
錢不夠 <input type="radio" value="我想多賺錢" name="r2">
想賺錢</font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080"> </font><font size="2" color="#66FFFF">
#</font><font size="2" color="#000080">訓練</font> <font size="2" color="#000080"><select name="select7">
<option selected>請選擇</option>
<option>我願意接受網路行銷課程&教育訓練課程</option>
<option>我不願意接受網路行銷課程&教育訓練課程</option>
</select></font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080">
網路行銷&教育訓練</font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080"> </font><font size="2" color="#66FFFF">
#</font><font size="2" color="#000080">住址</font>
<font size="2" color="#000080"><select name="City">
<option selected>台北縣</option>
<option>台北市</option>
<option>桃園縣</option>
<option>新竹縣</option>
<option>新竹市</option>
<option>苗栗縣</option>
<option>台中縣</option>
<option>台中市</option>
<option>彰化縣</option>
<option>南投縣</option>
<option>雲林縣</option>
<option>嘉義縣</option>
<option>嘉義市</option>
<option>台南縣</option>
<option>台南市</option>
<option>高雄縣</option>
<option>高雄市</option>
<option>屏東縣</option>
<option>台東縣</option>
<option>花蓮縣</option>
<option>宜蘭縣</option>
<option>基隆市</option>
<option>澎湖縣</option>
<option>金門縣</option>
<option>連江縣</option>
</select> <input size="30" name="Address"></font> </p>
<p align="left" style="margin-top: 3; margin-bottom: 0"> <font color="#66FFFF">#</font><font size="2" color="#000080">電話<input maxLength="15" size="17" name="Tel">
行動 <input maxLength="15" size="17" name="Act"></font><b><font size="2" color="#FF0000">必填</font></b></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#66FFFF"><b> </b>#</font><font size="2" color="#000080"> 聯絡<select name="select2">
<option selected>請選擇</option>
<option>星期一</option>
<option>星期二</option>
<option>星期三</option>
<option>星期四</option>
<option>星期五</option>
<option>星期六</option>
<option>星期日</option>
<option>週一~週日</option>
</select> <select name="select3">
<option selected>請選擇</option>
<option>上午9點~12點跟我連絡</option>
<option>中午12點~1點跟我連絡</option>
<option>下午1點~5點跟我連絡</option>
<option>晚上8點~10點跟我連絡</option>
<option>晚上9點~11點跟我連絡</option>
<option>上述時間都可以跟我連絡</option>
</select></font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080">
方便聯絡時間</font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080"> </font><font size="2" color="#66FFFF">#</font><font size="2" color="#000080"> 面談</font> <font size="2" color="#000080"><select name="select2">
<option selected>請選擇</option>
<option>星期一</option>
<option>星期二</option>
<option>星期三</option>
<option>星期四</option>
<option>星期五</option>
<option>星期六</option>
<option>星期日</option>
<option>週一~週日</option>
</select> <select name="select3">
<option selected>請選擇</option>
<option>上午10點~12點跟我面談</option>
<option>中午12點~2點跟我面談</option>
<option>下午1點~3點跟我面談</option>
<option>下午2點~4點跟我面談</option>
<option>下午3點~5點跟我面談</option>
<option>晚上6點~9點跟我面談</option>
<option>晚上7點~10點跟我面談</option>
<option>晚上8點~11點跟我面談</option>
<option>上述時間都可以跟我面談</option>
</select></font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080">
可以接受邀約進一步了解</font></p>
<p align="left" style="margin-top: 3; margin-bottom: 0">
<font size="2" color="#000080"> </font><font size="2" color="#66FFFF">#</font><font size="2" color="#000080">
信箱</font>
<font size="2" color="#000080"><input size="40" name="E"></font><b><font size="2" color="#FF0000">必填</font></b>
</p>
<p align="left" style="margin-top: 3; margin-bottom: 0"> <font color="#66FFFF">#</font><font size="2" color="#000080"><textarea name="SpeakMe" rows="1" cols="40">我要把握機會,請與我連絡!</textarea>
限500字</font> </p>
</td>
<td width="8" height="722" bgcolor="#FFCC00"> </td>
<td width="7" height="722" bgcolor="#808000"> </td>
</tr>
<tr>
<td width="403" height="54" bgcolor="#FFCC00" rowspan="2">
<font size="2" color="#000080"> <input type="reset" value="清除重來" name="clear"> <input type="button" value="放棄" name="giveup"></font>
<font size="2" color="#000080"><input type="submit" value="寫好送出" name="SineOk"></font></td>
<td width="8" height="29" bgcolor="#808000"> </td>
<td width="7" height="29" bgcolor="#FFFF00"> </td>
</tr>
<tr>
<td width="8" height="21" bgcolor="#FFFF00"> </td>
<td width="7" height="21" bgcolor="#FF9900"> </td>
</tr>
</table>
<tr>
</body>
</html>
<!-- v1YzNp-->
|
|
From: William M. K. <wm...@ix...> - 2003-01-10 18:25:14
|
Posted to comp.lang.cobol and IBM-MAIN - with BCC's to various people =
and
groups:
***
I have received information from a "usually reliable source" that it
currently looks like (but has not yet been finalized) that (as Thane =
Hubbell
stated a while ago) there *will* be a separate ANSI "version" of the
recently approved (in 2002 - but not yet finished processing by ANSI) =
COBOL
Standard. It *appears* as if the copyright statement will not be =
identical
to what the ISO document has. However, exact wording and "policies" are
still under review.
Possibly of *most* interest, the following pricing "clue" was given to =
me:
"I don't have any problem distributing the price information b/c that =
has
been around now (for at least four or five years) on all our documents
that are sold and any adoptions. ...
INCITS policy on all Adoptions of ISO/IEC specifications is that the =
US
adopted standard will be sold for $18 if purchasing the pdf format. ...
In fact when C++ adoption was approved we had many people globally
interested in the national adoption for $18. ISO was listing their =
document
as $245."
***
Please NOTE WELL:
Nothing is "final" until it is FINAL. Either I, or Thane (or Chuck
Stevens) will keep CLC posted on the status of this (and when/if it =
becomes
final)
--
Bill Klein
wmklein <at> ix.netcom.com
|
|
From: Chris M. <cob...@ni...> - 2003-01-08 22:42:44
|
Tim - Happy New Year! I'm just back from my extended vacation and I hope you are back as well. If you could send me the information on the inspect runtime routines, that will enable me to get my head wrapped around what's going on. As a side note, I am trying to setup two environments simultaneously ... a Win32 MINGW / MSYS based complier environment and also the Linux environment that Cobol For GCC is native to. I am hoping to discover where the deltas are between the Linux environment and Win32 environment. At the same time this is enabling me to learn the structure of GCC and the associated tools that are required for Cobol for GCC (such as autogen). My New Years resolution is to keep a journal on my website of what I've learned as I move along ... let's see if I can keep that resolution. Cheers, Chris At 01:52 AM 11/19/2002, you wrote: >Chris, > >Thanks for the update. It took me six months to get the signoff from my >employer, hope yours is quicker. > >I don't have many tasks on the site. You basically have a choice of a runtime >routine, or part of the compiler itself. The runtime is the larger part. Some >is pretty straightforward and some is more complex. > >There is a mailing list cobolforgcc-developers but it is not very active - >people prefer to email me directly for some reason ;-). > >My priorities for tasks would be > >a) Finish the inspect runtime routines that were partially completed (smallish >task) OR >b) Finish the sort/merge runtime (large). > >You may well decide to start either one from scratch rather than finish them, >up to you. > >If you want to work on the compiler proper, you need to spend some time >learning how gcc is structured, then it is just a matter of picking a verb. >Then you write the parse (cobcprs.tpl) the tree manipulation (cobcast.c) and >the code generation (cobcbei.c), as well as adding stuff to various header >files. Even adding the parsing for some verbs would be useful, even without >code generation. > >I will be away from 29 November to mid January. So it would be good to get a >task agreed before then. I willbe working on it while I am away but >communications will be difficult. > >Regards, >Tim Josling > >Chris Marshall wrote: > > > > Tim - > > > > Just wanted to give you an update on where I'm at. I've registered myself > > with FSF, and I'm 90% of the way through getting clearances from my > employer. > > > > I've been working on getting a stable development environment (somewhat > > unsuccessfully, but making progress) on GCC 3.2 working on both RedHat > > Linux 7.2 and the latest copy of MingW on Win32 in a Win2KPro environment. > > I've retrieved both the Cobol For GCC .tar.gz file from SourceForge as well > > as the current CVS codeline per the instructions on project website. > > > > I was looking for a list of open tasks on the SourceForge website and I > > wasn't able to find too much. I didn't know if that was because I wasn't > > listed as a developer on the project or not and if there were different > > views for developers vs. visitors. > > > > I haven't seen much activity on the cobolforgcc-devel lists. Are there > > other mailing lists that I should subscribe to keep up with the status / > > activities of the project? > > > > Cheers, > > > > Chris |
|
From: William M. K. <wm...@ix...> - 2002-12-07 00:05:45
|
(Sent to comp.lang.cobol with various CC's) The *APPROVED* ISO 2002 COBOL Standard is available from the ANSI online store at: http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+1989%3A2 002 for the bargain <G !!!> price of $215.00 U.S. Dollars. This will get you a PDF file - with NO permission to further distribute it or even copy "significant" text into other documents without prior permission. If you are outside the US, you might (???) want to look at purchasing this from ISO. See: http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=28 805&ICS1=35&ICS2=60&ICS3= This has the same copy/distribution restrictions - but only (???) costs 348.00 Swiss Francs. You may find that your "own" national standards body sells it (also) in "local currency". NOTE WELL: In addition to the copyright statement within the text, make certain you read AND UNDERSTAND the "EULA" (End User Licensing Agreement) when "purchasing" either of these documents. -- Bill Klein wmklein <at> ix.netcom.com |
|
From: William M. K. <wm...@ix...> - 2002-10-27 20:14:10
|
FYI,
I just sent the "following" note out to the comp.lang.cobol and
IBM-MAIN newsgroups. Please feel free to ignore it, (laugh at it), or
forward it to others who might be interested in it.
-----Original Message-----
Believe it or not (and consider it "good or bad" as you will <G>),
*** NOW ***
is the time for anyone interested in providing input into the *next*
COBOL
Standard (the one after the recently approved 2002 Standard) to provide
their input (including both ideas and PRIORITIES) to the COBOL
Standardization committees.
For a current list of items that have been suggested (some of which have
been discussed - others which have not), you can see the J4 document
"Candidate features for a future revision" at:
http://www.cobolportal.com/j4/files/02-0222.doc
Just because an item is listed there, please do NOT assume that it
either
will be or won't be on the "work plan" for the next revision. If you
have
input on this list (including items to ADD, Delete, or that you want to
express an opinion on its priority), you can do one of two things (and I
recommend the first). Also, just because an item (or concept) is
currently scheduled for a "Technical Report" before the next Standard,
do NOT assume that it will be in the next (or any) future COBOL Standard
(unless users indicate the need for it - and the "correct and stable
definition" for it being reached already.)
FYI - before "pursuing" this, you probably will want to review the
"Substantive Change" section of the 2002 Standard to see if the feature
that
you are interested in, has already been "included" - but isn't (yet)
available from your COBOL Vendor-of-choice.
1) Send a note to the J4 chair at:
Don.Schricker <at > microfocus.com
giving as MUCH detail as possible on what you want and why you want it
(and
where you rank its priority compared to other things - including length
of
time until next Standard, e.g.
"I want you to add feature XYZ - because we are forced to use
non-COBOL
features to do the following 'business task' ... and I want this feature
more than most/some/many of the other items currently listed in J4
document 02-0222.
Please do <not> add this feature if it will take more than (2? 3? 5?)
years
to process the next COBOL Standard."
2) If you are involved in COBOL "work" in some country outside the US,
then
you can send this same information to your national Standards body. For
a
list of how to contact such groups, see:
http://www.iso.org/iso/en/aboutiso/isomembers/MemberList.MemberSummary?M
EMBERCODE=10
(Going thru your own national Standards body *might* give it higher
priority
than going thru J4 directly - to which people from ANY country may
submit ideas.
However, it also may DELAY the processing - as the international group
will
PROBABLY end up referring it back to J4.)
P.S. If there is an idea listed in the "02-0222" document listed above
that
you want more information on. You can probably get this from the J4
chair.
Some of them already have detailed "suggestion" papers, some have only
sketchy suggestions, and some only have a sentence or two in some other
document. Alternatively, if your "vendor of choice" is represented on
the J4 committee, you might want to work thru their representative or
"user group". For the current membership list, see:
http://www.cobolportal.com/j4/files/02-0137.doc
--
Bill Klein
wmklein <at> ix.netcom.com
|
|
From: Tim J. <te...@me...> - 2002-10-19 08:04:45
|
wang lifeng wrote: > > > Hi. I just wanted to find out what was going on with this project, if it > > was still alive or not. Most of the information I've found on the web is > > about a year old. > > > > It has not been refreshed for a very very long time .Most of the examples > was written almost 2 years ago . > God knows. > > wanglf Have a browse of the CVS, and look at the test cases. You can see what was added when. Tim Josling |
|
From: Tim J. <te...@me...> - 2002-10-19 07:51:24
|
Bernard Giroud wrote: >=20 > Chris Marshall a =E9crit : >=20 > > Hi. I just wanted to find out what was going on with this project, if= it > > was still alive or not. Most of the information I've found on the web= is > > about a year old. > > > > Thanks! > > > > Chris > > > > >=20 > If you browse the CVS directory, you will find that Tim (Josling) is > working hard. But COBOL is a huge and tricky language, so > there's a lot to do. >=20 > But I agree that it is frustrating for people to see no progress. >=20 > Tim, would it be possible to release a tarball from time to time, > and to advertise them in comp.lang.cobol ? >=20 > Bernard Giroud >=20 As Bernard said, I am working hard on it. However it is not quite useful = yet so no announcements... As it turns out version 0.5 is "code complete". This constitutes enough o= f the language to be usable in writing the runtime routines. I am working on the documentation including web page updates, and an RPM package for Red Hat Linux. I hope that will be ready soon and I will anno= unce it in comp.lang.cobol. One of the issues with being an add-on to GCC is that it is not a simple matter of releasing a tarball. If people want to compile it themselves th= ey need to install the GCC source and then add cobol4gcc to that which is complex. Tim Josling |
|
From: Bernard G. <bg...@fr...> - 2002-10-19 07:17:41
|
Chris Marshall a écrit : > Hi. I just wanted to find out what was going on with this project, if it > was still alive or not. Most of the information I've found on the web is > about a year old. > > Thanks! > > Chris > > If you browse the CVS directory, you will find that Tim (Josling) is working hard. But COBOL is a huge and tricky language, so there's a lot to do. But I agree that it is frustrating for people to see no progress. Tim, would it be possible to release a tarball from time to time, and to advertise them in comp.lang.cobol ? Bernard Giroud |
|
From: wang l. <wa...@ne...> - 2002-10-19 01:06:47
|
> Hi. I just wanted to find out what was going on with this project, if it > was still alive or not. Most of the information I've found on the web is > about a year old. > It has not been refreshed for a very very long time .Most of the examples was written almost 2 years ago . God knows. wanglf > Thanks! > > Chris > > > > > --__--__-- > > _______________________________________________ > Cobolforgcc-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobolforgcc-devel > > > End of Cobolforgcc-devel Digest > > |
|
From: Chris M. <aut...@ni...> - 2002-10-18 17:09:35
|
Hi. I just wanted to find out what was going on with this project, if it was still alive or not. Most of the information I've found on the web is about a year old. Thanks! Chris |
|
From: <bur...@ya...> - 2002-09-30 12:10:26
|
Hi I would think this would be ideal for alot of users, myself I am trying to convert hp3000 cobol programs to tc , which has worked, where I have hit a wall is converting the db calls to work with MYsql, I will have to start using perl/php/c++ to write some wrappers, to gain more acceptance of the package it would be so useful to have these libraries to hand , other than that the conversion has worked fine, I have had to work on some post 85 functions which are not available on the tc but apart from that it works great. Peter Burgess --- Bernard Giroud <bg...@fr...> wrote: > Hi all, > > Good news and bad ones! > On the good news front, I'm very pleased of the > final > ratification of COBOL 2002 by the ISO. > On the bad ones, we (Opensource Cobol compiler > projects developers) have still a long way to go, > just to implement the 85/89 standard. > > I think it is about time to try to work a little > more > together, following the tracks of David Essex and > Keisuke Nishida. > > So many things need still to be done (not in any > order), > like : > - other file support systems (Inodb, RMS, ...) > - decent sort library and interface > - Sql preprocessor for ODBC and MySQL > - COBOL prettyprinter (like indent for C) > - integration into GDB, DDD and IDE's > ... > > So I propose the following (I think Tim did agree > on the principle): design a common libcob, and > if necessary, migrate the corresponding compilers. > > Just to start the discussion, I see two main > approaches: > either take an existing one, "donate" it to the > cobol > project, and upgrade to the specs, > or just start from scratch again. > > No surprise, I'm in favour of the first; but which > one? > Well, it might depend on the specs we adopt. > So I think the best start is the specs for: > - the way the cobol field is accessed from the > routine > - a descriptor for a cobol field > - a descriptor for a cobol file > > Just to start the ball rolling, I will send this > message > to the compilers mailing list, but I think the > discussion > should be carried on in the cobol-util ML. > > First of all, Keisuke, what was the reason behind > having a descriptor with two pointers, one for > the attr desc and the other for the data, except > economy of paramters for the routines and > possible factorisation of field_desc ? > > Hoping to concentrate forces ... > > Bernard Giroud > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Tin...@li... > https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com |
|
From: Bernard G. <bg...@fr...> - 2002-09-28 07:05:14
|
Hi all, Good news and bad ones! On the good news front, I'm very pleased of the final ratification of COBOL 2002 by the ISO. On the bad ones, we (Opensource Cobol compiler projects developers) have still a long way to go, just to implement the 85/89 standard. I think it is about time to try to work a little more together, following the tracks of David Essex and Keisuke Nishida. So many things need still to be done (not in any order), like : - other file support systems (Inodb, RMS, ...) - decent sort library and interface - Sql preprocessor for ODBC and MySQL - COBOL prettyprinter (like indent for C) - integration into GDB, DDD and IDE's ... So I propose the following (I think Tim did agree on the principle): design a common libcob, and if necessary, migrate the corresponding compilers. Just to start the discussion, I see two main approaches: either take an existing one, "donate" it to the cobol project, and upgrade to the specs, or just start from scratch again. No surprise, I'm in favour of the first; but which one? Well, it might depend on the specs we adopt. So I think the best start is the specs for: - the way the cobol field is accessed from the routine - a descriptor for a cobol field - a descriptor for a cobol file Just to start the ball rolling, I will send this message to the compilers mailing list, but I think the discussion should be carried on in the cobol-util ML. First of all, Keisuke, what was the reason behind having a descriptor with two pointers, one for the attr desc and the other for the data, except economy of paramters for the routines and possible factorisation of field_desc ? Hoping to concentrate forces ... Bernard Giroud |
|
From: William M. K. <wm...@ix...> - 2002-09-13 20:34:41
|
FYI (for those of you who don't currently follow comp.lang.cobol - or IBM-MAIN) I just posted the "following" to these groups. -----Original Message----- For those of you who might be interested, my "US public review comments" on the final draft of the COBOL Standard can be seen from the INCITS (US Standards body) web page at: http://www.incits.org/archive/2002/it02818r/it02818r.htm That page links to http://www.incits.org/archive/2002/it02818r/prcmt2_fdis1989.pdf FYI - Despite what I sent in (and what the only other public review comment received by the "due date" of Sep 9th said), it is my STRONGEST possible expectation that this will be an "official" ANSI and ISO Standard "around" year end (of this year). NOTE WELL: (This was sent to both comp.lang.cobol and IBM-MAIN). For those of you in an IBM environment (mainframe *or* workstation), all current indications are that IBM has no *current* plans to implement this full Standard. They have indicated that they will "consider" implementing specific features - based on user demand vs implementation resource requirements vs expected revenue. Although late public review responses need not be "fully responded to" - if you really DO want to send in a "late comment", you should follow the instructions at: http://www.incits.org/prsweb.htm I can't (personally) think of any "good reason" to do this, but that is up to every individual "COBOL interested" person. Final Note: This information ONLY applies to the ANSI (US) review process. If you are "involved" in COBOL in another country, you will need to contact your national Standards body to find out what (if anything) they have done about this final "approval step" of the next COBOL Standard. -- Bill Klein wmklein <at> ix.netcom.com |
|
From: William M. K. <wm...@ix...> - 2002-07-26 03:14:01
|
FYI - if you haven't already seen this. -----Original Message----- From: Don Schricker Sent: Thursday, July 25, 2002 8:06 PM The Working Draft Technical Report on Object finalization in COBOL is available on the INCITS/J4 web site: http://www.cobolportal.com/j4 - top link in body of page This document is available for informal review and comment. There will not be a formal public review until later stages in the development of the technical report. However, it is easier to change things at this point in response to comments, so I request you to review the document and send me your comments. Since this is an informal review, you will receive and acknowledgement of your comments, but no formal response. I will notify you when the updated version is available. Please inform other colleagues who may be interested in this subject. Don Schricker Micro Focus Product Manager, Language Standards Chairman J4, the COBOL technical committee of INCITS <mailto:Don...@mi...> Don...@mi... http://www.cobolstandards.com <http://www.cobolstandards.com/> http://www.microfocus.com <http://www.microfocus.com/> |
|
From: David E. <de...@ar...> - 2002-06-24 17:40:56
|
At 12:31 PM 19/06/02 +0900, Keisuke Nishida wrote: > I have registered COBOL Utilities Project on SourceForge: > > Can we move there? Yes, we should move some of the projects there. I think the first projects should be the NIST test suite. I think that the OC version should be the starting point, thus it should be checked in to CVS. David Essex |
4 messages has been excluded from this view by a project administrator.
![http://home.pchome.com.tw/mysite/wgs0212/bfh010016.gif">](http://home.pchome.com.tw/mysite/wgs0212/bfh010016.gif">){kind=link}
![http://home.pchome.com.tw/mysite/wgs0212/bfh010016.gif"](http://home.pchome.com.tw/mysite/wgs0212/bfh010016.gif"){kind=link}