Well, I graduated from CompSci about 15 years ago, but my work was never programming related.
About a year ago I started getting back into it to work on a hobby project. Since then I've dabbled in looked at many different languages.
I came across Icon and Unicon in that process and my first impressions were that it was simple enough for anyone to pick up as a first language, but powerful enough to do pretty much anything the "other" languages do.
Although I've not used it actively, I've kept tabs on it and actually is one of the first things I install whenever I install a new distro. I also have in my library paperpacks of the v2 and v3 Icon Programming language book, v2 of the Unicon book and a bunch of other tutorials I found along the way.
I think it's great you have opened up the discussion forum.
I also want to throw a kudos to Brian for the amazing body of work you have been putting together at http://btiffin.users.sourceforge.net/up/unicon.html . You are a skilled writer and have been enjoying reading through it. Do you intend to release a paperback?
That's it for introductions, hope to visit this forum regularly to annoy you with my questions ;)
Regards,
yves
Last edit: Yves Cloutier 2017-04-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I first came across Icon in 1986 and used it in a commercial
environment. I had been delegated to write a program to extract
accounting information form Unix log files for an internal transfer
pricing regime. The original development had been done in TurboPascal at
the time. The reason for the change of languages was due to the
constantly changing format of the supplied log files. From the time of
getting a copy of the Icon system to rewriting the entire program was 3
days. The code was a complete redevelopment. This included learning the
language as well. After the redevelopment, I didn't have a problem with
having to deal with the format changes. The program was written to
ignore these incessant changes. I loved it.
There have been many times over the years that I have installed Icon and
in this century Unicon on work computers so as to solve varied problems.
I have found that the language gives the facilities to solve problems at
a higher level than the other available programming resources.
I encourage you to use it actively and see the kinds of problems it
helps solve easily.
It has its quirks and there are definitely missing features, but on the
whole, I find it a much more comfortable language to program in that
many others.
You'll also find a group of very cluey people here who can answer most
of not all questions you may have. In addition, keep an eye on the
unicon mailgroup as interesting stuff comes up there from time to time.
If you want to see comparison programs (Icon/Unicon to other languages),
have a look at RosettaCode. People have put up good examples there.
regards
Bruce Rennie
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Although that will be a moving target, as I work toward a release 1.0. The last few months have not seen many updates as I've been busy with the GnuCOBOL project as we prep a 2.2 release. (Finally, after some 8 years of work since 1.1 rolled out).
I'm in Ottawa as well. Perhaps we can organize a two member Unicon User Group. :-) And have a meeting over coffee. And/or I should pester the Ottawa Carleton Linux User Group and host a talk at one of the monthly meetings. (They meet at Algonquin College off Woodroffe, the first Thursday of every month). http://oclug.on.ca/
Along with finishing up the Operators section (that chapter is sorely missing on details), I really want to see Unicon -C extended to produce object code that can be linked to other C programs (or COBOL actually, anything that handles the C Application Binary Interface). When we finally tag GnuCOBOL 2.2, that floats to near the top of the todo pile. I'm of the opinion that being able to produce linkable binary objects (and not just full programs) will up the appeal of Unicon a bit, and affect the mind share in a positive way.
The libffi layer is another extension that I'd like to finish up. It really makes linking to C libraries a breeze, with no external loadfunc wrapper code required, just pure Unicon.
Those, and getting the Try Unicon Now web compiler sandbox up and running. I have a local cut, but it'll take a few days to figure out how it can get linked into the main project space here on the forge in a safe manner. (Finding that time is currently a problem, but soon).
Same excuse for the Unicon code highlighter that should already be active here on SourceForge. I need to prep a pull request for the Pygments team. (The code highlighter I use in the UP docs is the same software (Pygments) that is used here on the forge. Once I get it prepped and accepted we should see Unicon/Icon and ucode listing in colour on these pages shortly there after). My bad, that should have happened months ago.
Thanks again, Yves.
Have good, make well,
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good to have you onboard. You will find many people here who are passionate about the language and who are eager to answer your questions and help you navigate through the various features of the language.
Dive in, and let us know when you have any question,
Cheers,
Jafar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks everyone. I have to agree, the unicon folks are a friendly bunch, as are the folks over at the icon list.
@brian: sure we could certainly meet up, though admitedly Woodroffe campus is a bit a ways off for me. I live downtown and without a car. Do let me know if you happen to be in the area some time. I'll wait a bit before printing off your PDF seeing as you're still working your way up to a 1.0 and still adding content. But far it's a great reference.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey, what do you know, same boat. OCTranspo for the errmm, win? ;-)
I'm not quite downtown, just off Beechwood near St. Pat's bridge.
Thanks again for the kudos. I should have been working on the Operators chapter, but I got distracted and played with the Performance section last night. Added numbers for a few more languages. Even with C speeds and the trendy powers inherent in things like Elixir, Unicon still floats to the top of the recommended list. Especially when loadfunc provides such easy access to bare metal when the need for speed overrides the need for speedy development.
I'll try and get a note sent to John Nash and pester OCLUG about setting up a Unicon talk. At the earliest it would be May 4th, but more likely June 1st or possibly later.
Have good. make well,
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone,
I'm a hobby programmer in Ottawa, Canada.
Well, I graduated from CompSci about 15 years ago, but my work was never programming related.
About a year ago I started getting back into it to work on a hobby project. Since then I've dabbled in looked at many different languages.
I came across Icon and Unicon in that process and my first impressions were that it was simple enough for anyone to pick up as a first language, but powerful enough to do pretty much anything the "other" languages do.
Although I've not used it actively, I've kept tabs on it and actually is one of the first things I install whenever I install a new distro. I also have in my library paperpacks of the v2 and v3 Icon Programming language book, v2 of the Unicon book and a bunch of other tutorials I found along the way.
I think it's great you have opened up the discussion forum.
I also want to throw a kudos to Brian for the amazing body of work you have been putting together at http://btiffin.users.sourceforge.net/up/unicon.html . You are a skilled writer and have been enjoying reading through it. Do you intend to release a paperback?
That's it for introductions, hope to visit this forum regularly to annoy you with my questions ;)
Regards,
yves
Last edit: Yves Cloutier 2017-04-07
Welcome Yves,
I first came across Icon in 1986 and used it in a commercial
environment. I had been delegated to write a program to extract
accounting information form Unix log files for an internal transfer
pricing regime. The original development had been done in TurboPascal at
the time. The reason for the change of languages was due to the
constantly changing format of the supplied log files. From the time of
getting a copy of the Icon system to rewriting the entire program was 3
days. The code was a complete redevelopment. This included learning the
language as well. After the redevelopment, I didn't have a problem with
having to deal with the format changes. The program was written to
ignore these incessant changes. I loved it.
There have been many times over the years that I have installed Icon and
in this century Unicon on work computers so as to solve varied problems.
I have found that the language gives the facilities to solve problems at
a higher level than the other available programming resources.
I encourage you to use it actively and see the kinds of problems it
helps solve easily.
It has its quirks and there are definitely missing features, but on the
whole, I find it a much more comfortable language to program in that
many others.
You'll also find a group of very cluey people here who can answer most
of not all questions you may have. In addition, keep an eye on the
unicon mailgroup as interesting stuff comes up there from time to time.
If you want to see comparison programs (Icon/Unicon to other languages),
have a look at RosettaCode. People have put up good examples there.
regards
Bruce Rennie
Thanks, Yves.
Not really, it is free documentation. Feel free to print out a copy of the PDF, available at
http://btiffin.users.sourceforge.net/up/UniconProgramming.pdf
Although that will be a moving target, as I work toward a release 1.0. The last few months have not seen many updates as I've been busy with the GnuCOBOL project as we prep a 2.2 release. (Finally, after some 8 years of work since 1.1 rolled out).
I'm in Ottawa as well. Perhaps we can organize a two member Unicon User Group. :-) And have a meeting over coffee. And/or I should pester the Ottawa Carleton Linux User Group and host a talk at one of the monthly meetings. (They meet at Algonquin College off Woodroffe, the first Thursday of every month). http://oclug.on.ca/
Along with finishing up the Operators section (that chapter is sorely missing on details), I really want to see Unicon -C extended to produce object code that can be linked to other C programs (or COBOL actually, anything that handles the C Application Binary Interface). When we finally tag GnuCOBOL 2.2, that floats to near the top of the todo pile. I'm of the opinion that being able to produce linkable binary objects (and not just full programs) will up the appeal of Unicon a bit, and affect the mind share in a positive way.
The libffi layer is another extension that I'd like to finish up. It really makes linking to C libraries a breeze, with no external loadfunc wrapper code required, just pure Unicon.
Those, and getting the Try Unicon Now web compiler sandbox up and running. I have a local cut, but it'll take a few days to figure out how it can get linked into the main project space here on the forge in a safe manner. (Finding that time is currently a problem, but soon).
Same excuse for the Unicon code highlighter that should already be active here on SourceForge. I need to prep a pull request for the Pygments team. (The code highlighter I use in the UP docs is the same software (Pygments) that is used here on the forge. Once I get it prepped and accepted we should see Unicon/Icon and ucode listing in colour on these pages shortly there after). My bad, that should have happened months ago.
Thanks again, Yves.
Have good, make well,
Brian
Hi Yves!
Good to have you onboard. You will find many people here who are passionate about the language and who are eager to answer your questions and help you navigate through the various features of the language.
Dive in, and let us know when you have any question,
Cheers,
Jafar
Thanks everyone. I have to agree, the unicon folks are a friendly bunch, as are the folks over at the icon list.
@brian: sure we could certainly meet up, though admitedly Woodroffe campus is a bit a ways off for me. I live downtown and without a car. Do let me know if you happen to be in the area some time. I'll wait a bit before printing off your PDF seeing as you're still working your way up to a 1.0 and still adding content. But far it's a great reference.
Hey, what do you know, same boat. OCTranspo for the errmm, win? ;-)
I'm not quite downtown, just off Beechwood near St. Pat's bridge.
Thanks again for the kudos. I should have been working on the Operators chapter, but I got distracted and played with the Performance section last night. Added numbers for a few more languages. Even with C speeds and the trendy powers inherent in things like Elixir, Unicon still floats to the top of the recommended list. Especially when
loadfuncprovides such easy access to bare metal when the need for speed overrides the need for speedy development.I'll try and get a note sent to John Nash and pester OCLUG about setting up a Unicon talk. At the earliest it would be May 4th, but more likely June 1st or possibly later.
Have good. make well,
Brian