|Subject:||Re: [Bug-GnuCOBOL] Debugger.|
|Date:||Mon, 8 May 2017 14:50:28 -0400|
3.0 release is planned for end of this year, but this heavily depends on
the number of issues found, the number of developers and the number of
people that taking care for people's question.
As there is no full-time developer for GnuCOBOL yet (no one offered this
until now, there was a project specific option but we missed it out, 2.0
not available as a release on this time was at least one of the reasons).
If all stays as it is now 3.0 may need until April 2018...
If SPLIT KEYs are a must (which I can understand - it is possible to do
this in COBOL with additional computed fields and my employer did this
when we converted our applications to OpenCOBOL 0.something so I could
be of help) then use reportwriter branch and consider moving to the
development branch once SPLIT KEYs and SPARSE KEYs are merged. As soon
as this happens these features get in the debugger branch (or, if
someone helps with fixing the issues of the debugger branch in the
meantime it will be available in development branch, too).
The main focus for now is the 2.2 release candidate, it should be out
since end of April 2017...
Am 08.05.2017 um 20:31 schrieb studiok:
> Any idea about 3.0 release's date?
> Split keys are my must.
> If gc-debugger does not handle them, i'm afraid I'all have to pospose my
> intention of working on it.
> In the while, i'll go and read the TODO.
> Il 08/05/2017 19:18, Simon Sobisch ha scritto:
>> Split keys are only supported in reportwriter and will be available in
>> the 3.0 release.
>> For the other program: if you provide a minimal sample raising this
>> issue I could check if I can fix the code generation that doesn't work
>> worth this sample.
>> For known issues with the not-yet-stable debugger branch see the TODO
>> file (you may find your issue listed there)
>> Am 8. Mai 2017 13:30:22 MESZ schrieb studiok <address@hidden>:
>> Hello Simon,
>> first test:
>> cobc -anim my-first-test-source.cbl informs that SPLIT KEYS
>> are not supported (reportwriter and official releas do).
>> cobc -anim my-second-test-source.cbl returns:
>> /tmp/cob1758_0.c:348:4: note: previous definition of ‘l_anim_1’ was here
>> /tmp/cob1758_0.c:506:4: error: duplicate label ‘l_anim_2’
>> How should I go on?
>> Marcello Marsile
|[Prev in Thread]||Current Thread||[Next in Thread]|