Updates to Unicon Programming Page

[Anonymous]

(I'm not sure this is the best forum, please direct me elsewhere if appropriate - thanks!)

The Unicon documentation at: http://btiffin.users.sourceforge.net/up/index.html is excellent and nicely laid out. I'd like to make a minor suggested change to the "Curousities" section of the Expressions discussion.
The second example currently reads:

  procedure main()
        every write(subproc())
  end

  procedure subproc()
        every suspend 1 to 3 & 4
  end

That code will display the 4, and only the 4, the expr_2 result of the conjugation.

    4

The key expression here is grouped as

     every suspend ((1 to 3) & 4)

1 to 3 succeeds, and conjugation produces expr_2 when expr_1 succeeds.

The code actually outputs the 4 three times, once for each interation of the (1 to 3) clause.
Also, the use of every in front of the suspend is redundant can be removed with no change in behavior.

[Brian Tiffin]

Will correct. It's been a while. I must have crossed a wire between the thinking and discussion and the writing.

Thanks,
Blue

[Jafar]

@btiffin, you have mentioned a while back that you would like to move the unicon docset sources to public domain, and maybe move hosting to Unicon's space, are you still planning to do that?

[Brian Tiffin]

I doubt I'll relicense to PD, Jafar, but the current GPL 3+ is maybe not the best choice, I'm never sure. I used GPL instead of FDL as I figure the docset has more code listings than prose, but I also tried (and probably failed the legaleze) to state that the copyright notices in individual listings override the docset license once extracted. I'm not even sure that's a valid stance or if it just makes the whole thing a morass of not-legal. ;-)

I've started looking at ways to smooth out sharing the docset for inclusion in the project space here. Current thoughts, lacking Admin permissions to just place files via sftp, is to host a Fossil in the btiffin user-web space on the forge, and have a script that you or Clint can run to pull the latest Sphinx build output for placement in the Unicon project-web space. So yeah, up for sharing and getting things hosted in the official Unicon spaces.

And I'll take suggestions.

Have good, make well,
Blue

[Jafar]

Having a script pull your build to Unicon space might be easy to do. I guess I used the wong terms in my previous reply. I didn't mean you give up your copy-right claims over the material, but myabe release the source to faciliate contribution/fix like the issue in the original post.

[Brian Tiffin]

Been pondering a couple of ways to do this, Jafar.

I could move (clone) the revision control Fossil on to SourceForge servers in the btiffin user-web space. This is allowed by the terms and conditions here, and there are already a few Fossil instances running with one line CGI access scripts behind the normal web servers used. Then just a few minutes of Admin work to add write access to a few user accounts inside the Fossil to allow updates to the source ReStructuredText files. Those users would need a local install of Fossil, a few Python packages out of PIP, Sphinx and a few Sphinx-contrib entries to run fossil sync (defaults to automatic distributed sync), make html and make latexpdf builds.

Then admins in the Unicon project space would just need to run a shell script/cron job to put the outputs into a project-web subdirectory and provide links.

Or, the Fossils can be hosted just about anywhere really, as long as the host is accessible.

Someone runs a site local build and adminds run a transfer script for sftp to the forge. I use

::bash
#!/bin/bash
cd ~/wip/writing/gcfaq/_build/html
cp -v ../../gcfaq.rst .
cp -v ../latex/GnuCOBOLFAQ.pdf .

sftp -r btiffin,open-cobol@web.sourceforge.net <<EOF
cd htdocs/faq
mput -r *
EOF

for hosting the GnuCOBOL FAQ book in the GnuCOBOL project space (we started on the forge as OpenCOBOL, and that name is still used in the SourceForge filesystem).

And

::bash
#!/bin/bash
#
# Unicon Programming doc transfer
#
cd ~/wip/writing/unicon/_build/html
cp -v ../latex/UniconProgramming.pdf .

sftp -r -b - btiffin,open-cobol@web.sourceforge.net <<EOF
cd /home/user-web/btiffin/htdocs/up
mput -r *
EOF

to host the current UP docs in my user-web space here on the forge. Pretty straight forward. The sftp command relies on a matching ssh public key (id_rsa.pub) stashed on SourceForge for the account under

Me -> Account Settings -> SSH keys sub tab, and then a copy'n'paste into the web form.

After that setup, I have the workflow down to make html, make latexpdf, look to ensure no bugs in the build, and forgeup (which is the above transfer script).

So yeah, let's see if we can't get something setup for sharing and for hosting outputs in proper Unicon project spaces. The SoureForge user-web and project-web spaces are pretty much just normal CentOS 7 shells, and terms and conditions are very developer friendly as to what can be hosted. I'm pretty sure SourceForge only restricts things like local Apache installs that might interfere with normal forge operations - and even then, if your project is a web application or networking project they still let you host demos, with no quotas).

So yeah, let's.

(Or, from the SourceForge Unicon Project under Admin/User permissions add btiffin to the Admin group, send me a preferred subdirectory name for under htdocs and I'll have a copy posted in the Unicon project space a few minutes later. A few minutes after that, and a top bar menu can be added to the Unicon SourceForge project main page to kick the UP docs view along with some other choice Unicon documentation entry points in a menu bar dropdown). Yeah, that was just me putting in another dig. Feel free to ignore, Jafar. But if you do decide to grant permissions I'd be in a position to take a far more serious kick at sandboxing a Try It Now page for compiling and running Unicon programs right on the forge from sources in a textarea with output to the user's browser.* Dig, dig.... :-)

First up, I'll take a look at getting the Fossil repository hosted from a spot that is shareable by anyone that may want to make clones and/or edits to the source inputs. Probably here on the forge in my user-web space.

I still have a plan for "Fossilized custom versions" that would allow anyone to make revision controlled local edits and add notes to their own copy of the docset. WIth or without distribution.

Have good, make well,
Blue