[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [open-cobol-list] optional ecosystem for OC, Second thoughts on Java
Re: [open-cobol-list] optional ecosystem for OC, Second thoughts on Java etc
Sun, 17 Mar 2013 11:21:23 -0400
On Sun, 17 Mar 2013 09:14:05 -0400
Patrick <address@hidden> wrote:
> The more I read about Cobol the fewer and fewer external libraries I
> really need, there is a lot built in.
> However to interact with scientific instrumentation I am sure I will
> need some and my problems can be solved in multiple ways, better to
> do it in the most OC community friendly way.
> There is already Cobol .net but like Bryan I am not crazy about
> closed source toolchains and it looks like mono has had serious
> setbacks recently. There is also the Glib world that can be used
> without GTK and QT libraries that can be used without a GUI.
> There is boost from the plain C++ world and there is Java.
> With Hitachi offering Java integration with there compiler Java seems
> like a good fit but Java worries me.
> Larry Ellison sounds like a psychopath:
> Java seems to have serious security flaws:
> and Oracle is bundling in bloatware:
> I am wondering what is the best ecosystem for the greater community?
> What are your needs?
In many years of writing COBOL the only time I have needed or
used subordinate libraries is in a situation where a fancy gui
window was needed. Tiny Cobol has an example or two of calling
e.g, Tcl/tk. The COBOL data entry window is pretty bare bones
whether done with SCREEN statements or individual DISPLAY/ACCEPT
OTOH The basic Linux or other *nix utilities are very useful. I call
them using a CALL SYSTEM USING "ls -l >listing" type statement.
For an interface to scientific instrumentation perhaps ADA would be
useful. I have never used it.
Free list of books for self-publishers:
PDF e-book: "Create Book Covers with Scribus"
available at http://www.booklocker.com/books/4055.html