Re: [open-cobol-list] Linux Mint Borked?

[Patrick]

Thanks Brian and thanks again Mike

I am still trying to piece together what went wrong  but it looks like 
things started to go bad on Mint Linux when I tried to embed Jim Tcl(a 
tiny Tcl implementation) and used this command cobc -x jim.cob -ljim .

It failed and then I tried Brain's cobpy.cob program and it failed too, 
only it was my mistake as I used a -lpython flag instead of a 
-lpython2.7 flag.

I made other mistakes as well.

Now that I am on Debian, cobc -x jim.cob -ljim works just fine. I think 
it's jim on Mint that may be borked and what caused me to go off on a 
tangent.

Thanks again for all your support.

I am really happy tonight, I have jim working well with Cobol. I want to 
tidy up some examples and then share.

Jim Tcl is used in a similar way to Lua but Lua has much more market share.

I think jim may be better suited for working with Cobol then Lua. Lua 
numbs the pain of working in C but with Cobol we just don't have the 
same kind of pain and I don't personally need Lua right now.

The main weak points I have seen and heard about with Lua are the module 
system, suitability for shell scripting and regular expressions.

Jim is not nearly as powerful or fast as Lua but with jim these 3 topics 
appear strong and are what I think will add benefit to Cobol. There is a 
great deal of overlap between the strengths of Cobol and Lua.

I will be back with my results soon, I hope I will have something that 
will be of help to someone else on the list.