On 2016-08-18 07:22, Sergey Logichev wrote:
> Hello Brian,
>
> It sounds very hopefuly to have discussion forum with highliting
> feature for Unicon sources. Suppose, the search also will be available
> (Sphinx?). Hope you will find the understanding with all concerned
> people and teams.
>
> As for https access "bug" - it's unfortunately not supported currently
> by Unicon. I think Clint will tell you about it more detailed. But you
> can use workaround to get https (or ftp or any other) access from
> Unicon. Just use curl utility from https://curl.haxx.se/
> For example,
>
> datafile := "c:\\tmp\\q.q"
> url := "https://some-url/q.q";
> rc := system("curl --output "||datafile||" "||url)
> if /rc then stop("can't run curl")
> w := open(datafile,"r")
> ...
>
> Of course you should add bin path of curl to PATH environment variable
> to run it from Unicon.
>
> Best regards,
>
> Sergey
Thanks, Sergey (you'll be getting a near duplicate of this note, I
neglected to Reply-All to let the list see this post),
I have a build with SSL enabled already
unicon -features
...
secure sockets layer encryption
...
But I think I need to do a little more setup/configuring on my end.
https is not "supported" supported but it's available in the code. :-)
And yeah, for that little sample, a pipe would work as well.
p := open("curl -s https://sourceforge.net/projects/unicon/";, "p") |
stop("Cannot curl")
while write(read(p))
close(p)
For now, the plan is to get better at debugging the runtime and be able
to track which line is failing. Then figure out if it is a local
problem, or the platform, or something systemic.
Or, plan B, wait for the professionals to keep making things better and
supersede the reporting. :-)
So many things to explore... Oh, and Discussions are SourceForge are
turned on, so check out
https://sourceforge.net/p/unicon/discussion/
Be wary of the Allura SimpleMDE markdown editor everyone. It is in
Javascript, and bypasses things like FormHistoryControl (if you are like
me and end up clicking off page before hitting Post). The
FormHistoryControl browser addon is normally a lifesaver, but Javascript
editors and the ease of clicking back or a link to test something
leading to total webform data loss; it's like we're back in the save
early save often days of early PCs. I blame young people, those yet to
be born back in 1984. :-)
Have good,
Brian
> 18.08.2016, 06:46, "btiffin" <[email protected]>:
>
>> Hello, everyone
>>
>> Clinton? Would you be willing to turn up the Discussion feature on
>> the
>> SourceForge project space? I've been managing the GnuCOBOL project
>> space there, and it's a pretty good forum, out of some few thousand
>> threads, and many tens of thousands of posts, we've had to deal with
>>
>> only 3 pieces of spam, and that's with one of the groups (Help
>> getting
>> started) open to anonymous, unregistered submissions.
>>
>> This is still pending, but the Pygments lexer is coming along as
>> part of
>> the docset I'm working on (long roadmap, 100 pages in and it's still
>> not
>> even a full outline, let alone getting into any nitty-gritties),
>> Syntax
>> highlighted listings make for a better conversation, in my humble
>> opinion, and thread web pages seem a little accessible than just a
>> mailing list. The highlighter won't be visible on the forge until I
>> get
>> the code accepted by team Pocoo for the Pygments layer, and then
>> it'd be
>> another wait until a source release makes it to the Allura team, but
>> it
>> will be in the not too distant future.
>>
>> I know it can split focus, but the project space there already hosts
>> the
>> mailing lists, so access to the archives will always be visible on
>> the
>> top-level menu of the Allura Unicon space, along with a Discussion
>> tab
>> (if you deem it worthy of turning on).
>>
>> Just curious, and a little bit hopeful. I find it more accessible,
>> even
>> with the bad rap the previous owners (Dice) tainted SourceForge
>> with.
>> The new owners (BIZX) seem quite a bit more concerned about
>> reputation
>> then scraping nickels with sleazy tactics. I see it as a fight with
>> good
>> speech to drown out the bad.
>>
>> Next up; how fixed is the 22 (MVS) and 13 (everybody else) column
>> showline tracer field widths? I find -t with 13 character filename
>> space way too short. I've tweaked my own copy or rdebug.r to go out
>> as
>> far as 26, (with a 5 digit line-number field, as I'm thinking that a
>>
>> 10,000 line Unicon program is not that far of a stretch. Large, yes,
>>
>> but with some of the features in Unicon, programming in the large
>> doesn't seem to be a restriction). But, not knowing the ins and outs
>> of
>> all the support utilities yet, I'm wondering what tracer support
>> programs that will break, or if you'd be up for accepting a patch
>> request? Thought I'd ask here before I get too used to the extra
>> wiggle
>> room provided by 26 characters in the filename slot.
>>
>> http://peoplecards.ca/unicon/statements.html#suspend (for example)
>>
>> Next;
>> I have to do a little more testing, but I'm getting a segfault with
>> https access.
>>
>> #
>> # Try https
>> #
>>
>> procedure main()
>> w := open("https://sourceforge.net/projects/open-cobol/";, "m")
>> |
>> stop("Can't")
>> line := read(w)
>> write("Line: ", line)
>> while write(read(w))
>> end
>>
>> prompt$ unicon https.icn -
>> Parsing https.icn: .
>> /home/btiffin/inst/langs/unicon-svn/bin/icont -c -O https.icn
>> /tmp/uni21056032
>> Translating:
>> https.icn:
>> main
>> No errors
>> /home/btiffin/inst/langs/unicon-svn/bin/icont https.u -x
>> Linking:
>> Executing:
>>
>> Run-time error 302
>> File https.icn; Line 6
>> memory violation
>> Traceback:
>> main()
>> open("https://sourcefo.. [1].","m") from line 6 in https.icn
>>
>> This is rev 4470 on a 64bit Ubuntu node, but I'll do a little more
>> digging before making a bug report. I may well have a borked openssl
>>
>> config, blended with gnutls.
>>
>> And lastly;
>>
>> Thanks again for Unicon, Clint, Jafar, Steve, Robert and crew.
>> Having
>> way too much fun, and the rabbit holes are a code spelunker's
>> delight.
>> Next few days will be getting used to all the neato tools that
>> Robert
>> Parlett has written up. Deep, rabbits, Mmmm.
>>
>> Have good, make well,
>> Brian
>>
>>
> ------------------------------------------------------------------------------
>> _______________________________________________
>> Unicon-group mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/unicon-group
>
>
> Links:
> ------
> [1] https://sourcefo../
------------------------------------------------------------------------------
_______________________________________________
Unicon-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unicon-group
