KTSnowy

13 ms·

1.
Otterkit COBOL Dev Update 2: Syntactic analysis is now complete(github.com)
1 points by KTSnowy 3y ago|1 comments
2.
by KTSnowy 3y ago
After ~11500 lines of handwritten recursive descent, we finally finished implementing the whole syntactic analysis stage of the parser, which means that Otterkit can now syntactically and structurally understand the full Standard COBOL 2023
3.
Show HN: Otterkit.Numerics, WIP IEEE-754 Decimal Math Library for C#(github.com)
2 points by KTSnowy 4y ago|0 comments
4.
Otterkit COBOL Compiler on the .NET Community Standup(youtube.com)
2 points by KTSnowy 4y ago|1 comments
5.
by KTSnowy 4y ago
Hi, I'm the lead developer of Otterkit, a new free and open source COBOL compiler. We've been recently invited by the awesome .NET team to appear live on their Languages & Runtime Community Standup. We'll be talking about
6.
by KTSnowy 4y ago
> Is it really a transpiler? Why not directly compile to CIL? The end result of running Otterkit will be an executable or a C# DLL, so compiler would still be the most accurate word to describe it. If it stopped at the translation stage
7.
by KTSnowy 4y ago
Let me know if your company needs any particular features from a third-party COBOL dialect. We could work together to implement compiler support for those and ensure it works with your codebase. COBOL really needs more free and open source
8.
by KTSnowy 4y ago
Yes, exactly. Specially when paired with dotnet NativeAOT when deploying to a serverless service, could save a bit on server costs.
9.
by KTSnowy 4y ago
I know about GnuCOBOL, but both projects have different goals and ideals. Otterkit compiles to C#, and GnuCOBOL compiles to C. The two are meant for different use cases. You wouldn't use a huge C program in a .NET backend, it would be
10.
by KTSnowy 4y ago
Sent you an email. Is there anything you want to discuss that can't be done here publicly?
11.
by KTSnowy 4y ago
I understand, but this is an open source compiler. It's meant to be used by anyone who is interested in the language, or maybe by companies that wish to replace their quite expensive compiler licensing fees with an open source solution
12.
by KTSnowy 4y ago
Given the amount of proprietary and paid-to-use COBOL compilers which run on .NET and the JVM, I would say that you're not correct. It does in fact run on .NET already. The fact that there is a COBOL 2022 standard (yes, it's still
13.
by KTSnowy 4y ago
I find COBOL to be a very interesting language, with a huge unexplored potential. For example, I'm sure that most people are not aware that COBOL has generics, method overloading, declarative error/exception handling, asynchronous
14.
by KTSnowy 4y ago
We're planning to make a COBOL <=> C# bridge library, which will allow you to call C# methods from COBOL. The idea will be to find a way to expose C# classes and methods using COBOL's existing syntax. We still need to figur
15.
Show HN: Otterkit – COBOL compiler for .NET(github.com)
192 points by KTSnowy 4y ago|77 comments