Activity for Kevin Lyda
-
Kevin Lyda posted a comment on discussion GnuCOBOL
Sorry for the delay in updating this. There was a slight detour caused by a Lego Millennium Falcon. And tomorrow I have a few meetings, but should get time to get to the next pass of this.
-
There's also doc/opencobol.pdf and contrib/tools/printcbl/printcbl.pdf - should I also remove them? I'll republish in a bit with your list. (edit: actually won't be till tonight 29/9 due to power outage) Oh, and the svn revisions are stored in the comments so we can tie them together from that.
-
There's also doc/opencobol.pdf and contrib/tools/printcbl/printcbl.pdf - should I also remove them? I'll republish in a bit with your list. Oh, and the svn revisions are stored in the comments so we can tie them together from that.
-
There's also doc/opencobol.pdf and contrib/tools/printcbl/printcbl.pdf.
-
Hm. Github does not follow git replace grafts. Git clients will though.
-
Ah, nifty. I'll look at changing that. Would the fixed <-> free format conversion be useful?
-
(note, attempted to post this before and SF was down again; trying again) Per a conversation with Simon I went and combined the CVS and subversion repos into a single one. I think Simon's intent was an subversion one, but we can look into migrating it back afterwards. It's just easier (for me at least) to manipulate repos in git. This repo is split into three branches: meta/2017-migration - Which contains the notes and scripts needed to do the migration. cvs/import-review - this is the imported CVS...
-
Would a fixed<->free switching tool be useful? And I can look at a :Cobcompile, interesting.
-
If there are other common COBOL tasks that people can think of I'm happy to add them.
-
OK. That has not been my experience, but clearly it has been yours.
-
Oh, and you can get me at kevin@phrye.com. Is there an irc channel people tend to use?
-
OK, turns out I don't need that. The missing email list has grown larger. Also a list of the generated stuff you'd like removed would be good. Just some ideas what to look for. I'll post up a link tomorrow.
-
For what it's worth I second this. Making pretend that a file-system is case-insensitive when it really isn't is just a bunch of frustrating problems waiting to happen. I have to deal with a perl application that got dropped in my lap where the developer set MySQL up to ignore case in table names. Migrating it to a managed MySQL hosting provider was atrocious.
-
I get this: C:\src\cobol>cobol seq2rel; Microsoft (R) COBOL Optimizing Compiler Version 5.0 COBOL software by Micro Focus Copyright (C) Microsoft Corporation 1984,1993. All rights reserved. Copyright (C) Micro Focus Ltd. 1984,1993. All rights reserved. * Checking complete with no errors - starting code generation * Data = 000000858 Code = 000000761 C:\src\cobol>link seq2rel,,,lcobol+cobapi/nod; Microsoft (R) Segmented Executable Linker Version 5.31.009 Jul 13 1992 Copyright (C) Microsoft Corp 1984-1992....
-
Oh, and for scripting, I tend to do python or, if not available, lua. Though lua is rather goofily version sensitive. However I tend to use scripting languages to glue compiled tools together, not to be called from compiled languages themselves.
-
Sure. No problem. In the project there's a cvs repo and an svn repo. ISTR it works better if I have access to the CVSROOT on disk - so maybe send me a link to a tarball of that? I'll look at it tomorrow. One thing that would help would be to fill in the missing emails in this post.
-
My goal is a rather portable COBOL implementation of git. Possibly not all of it, but enough to do some basic, local operations. There's a lot to do though and I'm still on the "learn cobol step." But I'm semi-retired so I have a fair bit of time to devote to this.
-
I hadn't seen developers using Windows for well over a decade before coming across them the last few years. What blew my mind was just how crap their development environments were. They'd have multiple git/ssh/bash installs and would have little idea where their ssh keys were stored. They'd edit code with various IDEs that would upgrade randomly and break settings. I've kept my home directory in version control for nearly two decades at this point. First in CVS, then svn, then mercurial and finally...
-
I'm not clear on how that argument follows. The vast majority of computing on the planet is Linux based at this point. Android alone by far outpaces Windows sales. My former employer uses millions of Linux servers - as do quite a few other companies. And now even Windows has a Linux subsystem precisely because of the tools Linux brings to the table. As someone who has worked in places that use(d) RCS, SCCS, CVS, subversion, mercurial, perforce and git, I'm pretty familiar with this problem space....
-
Just curious, are there good options for getting access to other COBOL compilers to test portability and the like?
-
Still learning COBOL so no progress on actual code. But as I work through examples I wrote this up for making line numbering easier in fixed format files: https://github.com/lyda/vim-cobol
-
Long term I'd prefer a pure[0] COBOL solution, but this will do. Well. Almost. My sole need for MD5 is to MD5 files. In C I'd just do this with MD5_Init, MD5_Update and MD5_Final. Reading through data types I see there is a pointer in COBOL. So would I just create a COBOL pointer, pass that to the three MD5_ functions and then return the result from the MD5_Final? Hm... No, it would need some amount of space allocated to it...
-
It's been a long time since I've used subversion and it's way easier for me to navigate sources with git. My tracking down of where the GCic compile issue was done with git bisect for instance. Plus I have a few things I'd like to try. So I'd like to maintain a git mirror of GNU COBOL. Initially I'd just host it privately for myself (I have a pokey net connectionat times) but if some of my experiments work I can open it up and show it off in case people are curious. However to do it right, I'd prefer...
-
This is the revision where it broke: https://sourceforge.net/p/open-cobol/code/2060/
-
Ah, but this version does work: % cobc (GnuCOBOL) 2.0-rc3.0 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Keisuke Nishida, Roger While, Ron Norman, Simon Sobisch, Edward Hart Built Sep 12 2017 15:53:29 Packaged Nov 05 2016 15:27:33 UTC C version "5.4.0 20160609"...
-
Also tried it with the current version in trunk and got the same error: % cobc -V cobc (GnuCOBOL) 2.3-dev.0 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Keisuke Nishida, Roger While, Ron Norman, Simon Sobisch, Edward Hart Built Sep 12 2017 15:47:55 Packaged...
-
I'm also seeing errors. Specifically: % cobc -V cobc (GnuCOBOL) 2.2.0 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Keisuke Nishida, Roger While, Ron Norman, Simon Sobisch, Edward Hart Built Sep 11 2017 13:44:21 Packaged Sep 06 2017 18:48:43 UTC C version "5.4.0...
-
Ha! Yes.
-
Well, for the reason I described above I need MD5 as that's the hash git uses.
-
Is there an automated way to convert C to COBOL? That would make learning things a bit easier. Kevin
-
I put it up here: https://gist.github.com/lyda/239cfad690beb364c55df440c3e9ec39
-
The readme file says the following: We've seen a number of requests for a COBOL implementation of the popular cryptographic hash function MD5. MD5 is widely used for file checksums and similar purposes. It's also widely used for digital signature hashes and message authentication codes, though due to recent successful attacks it's no longer preferred for those purposes. It's still useful for many purposes, though. The MD5 algorithm is freely available and legally unencumbered, and a COBOL implementation...
-
Thanks for this. Seriously, impressive. I'll see about debugging it. Might be an issue with the value length? I realise this was a rather complicated program to start with learning. :) My eventual goal is a git implementation in COBOL. Not for any particular reason, just for the humour value. I might ask for code reviews as I go along - though this isn't going to be the highest priority project so it won't go all that fast. So for that purpose, the bitwise operators are needed. Calling out to a C...
-
Thanks! Will try and get that working later this week.
-
Using your git repo as a base, I built a Go version. I'm mainly using it as a prometheus...
-
Changes for RPM packaging; update readme.
-
Make a 1.7 release - 2 new warnings.
-
Need git to do a build.
-
Merge branch 'spahan' into spahan-merge
-
Language cleanup.
-
Add gitlab testing.
-
Set the version number correctly.
-
Fix arg parsing again. Sigh.
-
I love the pypy docker image. Also, sarcasm.
-
Make pypy have a python link.
-
Fun with python, bytes and utf8.
-
Add test coverage.
-
Fix whitelisted users.
-
Warn for files that do not exist.
-
Add home badges.
-
Fix option parsing for real.
-
Add version info.
-
Make the -q switch more effective.
-
Fixes to get versioning working.
-
Add .gitlab-ci.yml so I can test locally.
-
Spel chek.
-
Fix nonexistant file error.
-
Add pypy test support.
-
Test coverage doesn't seem to work on pypy3.
-
Add a contribution guide.
-
Add a basic changelog.
-
Fix option parsing for real (fix options access).
-
Use subprocess module.
-
Fix sending commit note email to id instead email
-
Result of misspellings run.
-
Merge branch 'master' into logo-white-compress
-
Reduce image size.
-
Another optipng run over png's.
-
Also optimise gifs with gifsicle.
1
