tcllib-devel — Discussion of development for tcllib

[Tcllib-devel] Critcl 3.1.18 released

[Andreas K. <aku...@sh...>]

Hello all.

Critcl 3.1.18 has been released today.

  C Runtime In Tcl, or CriTcl, is a system for compiling C code
  embedded in Tcl on the fly and either loading the resulting objects
  into Tcl for immediate use or packaging them for distribution. Use
  CriTcl to improve performance by rewriting in C those routines that
  are performance bottlenecks.

The full set of changes since 3.1.17 is in the commit log.

A smaller overview can be found at

  http://andreas-kupries.github.io/critcl/doc/files/changes.html

Focusing that list even more, on the new features:

  * (Developer support). Merged pull request #96 from
    sebres/main-direct-invoke. Enables direct invokation of the
    "main.tcl" file for starkits from within a dev checkout,
    i.e. outside of a starkit, or starpack.

  * Added channel types to the set of builtin argument and result
    types. The argument types are for simple channel access, access
    requiring unshared channels, and taking the channel fully into the
    C level, away from Tcl. The result type comes in variants for
    newly created channels, known channels, and to return taken
    channels back to Tcl. The first will register the returned value
    in the interpreter, the second assumes that it already is.

  * Package `critcl::class` bumped to version 1.1. Extended with the
    ability to create a C API for classes, and the ability to disable
    the generation of the Tcl API.

  * Package `critcl::cutil` bumped to version 0.2. Added macros
    ALLOC_PLUS and STRDUP.

  * Package `critcl::iassoc` bumped to version 1.1. Refactored
    internals to generate an include header for use by .c files. This
    now matches what other generator packages do. The template file is
    inlined and removed.

  * New package `critcl::callback` providing C-level functions and
    data structures to manage callbacks from C to Tcl.

  * Package `critcl::literals` bumped to version 1.3. Added mode
    `+list` enabling the conversion of multiple literals into a list
    of their strings.

  * Package `critcl::enum` bumped to version 1.1. Added basic mode
    handling, supporting `tcl` (default) and `+list` (extension
    enabling the conversion of multiple enum values into a list of
    their strings).

  * Package `critcl::emap` bumped to version 1.2. Extended existing
    mode handling with `+list` extension enabling the conversion of
    multiple emap values into a list of their strings.

  * Extended the set of available types by applying a few range
    restrictions to the scalar types (int, long, wideint, double,
    float).

        Example: `int > 0` is now a viable type name.

        This is actually more limited than the description might let
        you believe.


Wrt the restricted scalar types, it is the cartesian of

        (int, long, wideint, double, float)
      x (<, <=, >, >=)
      x (0, 1)

-- 
See you,
	Andreas Kupries <aku...@sh...>
			<https://core.tcl-lang.org/akupries/>
	Developer @	SUSE Software Canada ULC
		  	<and...@su...>

Tcl'2019, Nov 5-8, Houston, TX, USA. http://www.tcl.tk/community/tcl2019/
-------------------------------------------------------------------------------

[Tcllib-devel] Tklib 0.7 Released

[Andreas K. <aku...@sh...>]

Hello all.

The Tklib 0.7 Release has finally been made and tagged.

And no, the version number is not a reference to the seven years since
the previous release.

Technote:
	https://core.tcl-lang.org/tklib/technote/545a7ee378a0cc271fcf58ebf83684fb42570
94e

Updated:
	https://www.tcl-lang.org/software/tklib/
	https://wiki.tcl-lang.org/page/tklib
	https://wiki.tcl-lang.org/page/Tklib+Contents

-- 
See you,
	Andreas Kupries <aku...@sh...>
			<https://core.tcl-lang.org/akupries/>
	Developer @	SUSE Software Canada ULC
		  	<and...@su...>
-------------------------------------------------------------------------------

Re: [Tcllib-devel] Tklib 0.7 Release - Candidate 1 - Please test

[Andreas K. <aku...@sh...>]

> Am 09.01.20 um 17:48 schrieb Andreas Kupries:
> > 
> Hi Andreas,
> 
> Many thanks, now it is fully clear to me (I should have had a closer 
> look at localdoc.tcl rather than bothering you with my questions).
 
> A different question: I have just released version 1.4 of the
> Scrollutil package.  Prior to doing this, I performed a few
> last-minute corrections in its README.txt file.  I did the commit in
> trunk.

> Since I am not quite sure whether you will do the tklib release from
> the tklib-0-7-rc branch or from trunk (after merging the branch, of
> course), I am asking you whether I should merge these changes from
> trunk into the tklib-0-7-rc branch, in order to make sure that they
> will be contained in tklib 0.7.

As the release manager I will do the release from the tklib-0-7-rc
branch, and merge/cherry pick whatever is needed from the trunk into
it.

I have now done this for the README changes you mentioned.
Thank you for the note.

-- 
See you,
	Andreas Kupries <aku...@sh...>
			<https://core.tcl-lang.org/akupries/>
	Developer @	SUSE Software Canada ULC
		  	<and...@su...>

Tcl'2019, Nov 5-8, Houston, TX, USA. http://www.tcl.tk/community/tcl2019/
-------------------------------------------------------------------------------

[Tcllib-devel] Tklib 0.7 Release - Candidate 1 - Please test

[Andreas K. <aku...@sh...>]

Pushing on making a release for Tklib.

See
	https://core.tcl-lang.org/tklib/timeline?r=tklib-0-7-rc

for the branch this work is happening on.

With commit [1] we are now at RC 1.

With regard to testing

- Most packages have no such.

- Plotchart passes.

- widgetPlus has some 42 failures which look to be something around
  event loop handling and scroll callbacks. The tests apparently
  expect a scroll callback which does not happen in my environment.
  This is after me making some of the tests sort of work by
  initializing various global variables expected to be set by the
  missing callback.

  Keith, please advise.

  My environment:

	Platform: Linux amd64
	Core:	  8.4.20, 8.5.19, 8.6.9
	With:	  tcllibc

Please test this revision in your environments as well.

Note, while I am aware of the Tcl 8.7a3 and 9.0a1 RCs these are still
alpha releases. I have not tested against them, I do not plan to test
against them yet, and test suite failures against them are not release
blockers.

I am looking towards making the release on the Jan 17-19 weekend,
i.e. 1.5 weeks from now.


My test controller:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#!/bin/bash
set -x

log=${1:-ALL}

clear
echo

rm -f                           ../${log}.*
time nice ./sak.tcl test run -l ../${log} "$@"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~
[1] https://core.tcl-lang.org/tklib/info/033de041f70d2dd1

-- 
See you,
	Andreas Kupries <aku...@sh...>
			<https://core.tcl-lang.org/akupries/>
	Developer @	SUSE Software Canada ULC
		  	<and...@su...>
-------------------------------------------------------------------------------

[Tcllib-devel] Tcllib 1.20 Released

[Andreas K. <aku...@sh...>]

For the details please see

https://core.tcl-lang.org/tcllib/technote/cd3a11c3065120d491009e64a19f767617604
5cd

-- 
See you,
	Andreas Kupries <aku...@sh...>
			<https://core.tcl-lang.org/akupries/>
	Developer @	SUSE Software Canada ULC
		  	<and...@su...>
-------------------------------------------------------------------------------

[Tcllib-devel] Tcllib 1.20 Release - Candidate 2 - Please test

[Andreas K. <aku...@sh...>]

Finally managed to continue the work on Tcllib release 1.20.

See
	https://core.tcl-lang.org/tcllib/timeline?r=tcllib-1-20-rc

for the branch this work is happening on.

With commit [1] we are now at RC 2.

It passed the testsuite for me:

	Platform: Linux amd64
	Core:	  8.4.20, 8.5.19, 8.6.10 (*)
	With:	  tcllibc

Note: Used a near-release 8.6.10 build. Should still work with
8.6.9. (See commit [2] for notes and changes to the testsuite to make
that happen).

Please test this revision in your environments as well.

Note, while I am aware of the Tcl 8.7a3 and 9.0a1 RCs these are still
alpha releases. I have not tested against them, I do not plan to test
against them yet, and test suite failures against them are not release
blockers.

I am now preparing things to make a release coming Friday, or that
weekend.

~~~
[1] https://core.tcl-lang.org/tcllib/info/a198fe68f53d1edc
[2] https://core.tcl-lang.org/tcllib/info/b99647b03197a5cb

-- 
See you,
	Andreas Kupries <aku...@sh...>
			<https://core.tcl-lang.org/akupries/>
	Developer @	SUSE Software Canada ULC
		  	<and...@su...>

Tcl'2019, Nov 5-8, Houston, TX, USA. http://www.tcl.tk/community/tcl2019/
-------------------------------------------------------------------------------

[Tcllib-devel] Schedule Up - 26th Annual Tcl/Tk Conference (Tcl'2019)

[<con...@tc...>]

Hello tcllib-devel, fyi ...

26th Annual Tcl/Tk Conference (Tcl'2019)
https://www.tcl-lang.org/community/tcl2019/

November 05 - 08, 2019
Crowne Plaza Houston River Oaks
2712 Southwest Freeway, 77098
Houston, Texas, USA

[ NEWS
  * Our keynote speaker is [Will Duquette](https://github.com/wduquette)
    talking about "Tcl, Rust, and the Death of Rube Goldberg"

  * Registration is open. Please have a look at

    https://www.tcl-lang.org/community/tcl2019/register.html

  * The tutorials are known. See

    https://www.tcl-lang.org/community/tcl2019/tutorials.html
]

And our schedule for this year is now available at

    https://www.tcl-lang.org/community/tcl2019/schedule.html

This is the last general mail for the year.

Conference Committee

   * Andreas Kupries
   * Arjen Markus    Deltares
   * Brian Griffin   Mentor - A Siemens Business
   * Gerald Lester   KnG Consulting LLC
   * Joe Mistachkin  Mistachkin Systems
   * Ronald Fox      CAEN Technologies
                     NSCL @ Michigan State University

Contact Information     tcl...@go...

Tcl'2019 would like to thank those who are sponsoring the conference:

   * FlightAware
   * Mentor - A Siemens Business
   * Noumena Corp

[Tcllib-devel] 4th Call For Papers - Extended Deadline - 26th Annual Tcl/Tk Conference (Tcl'2019)

[<con...@tc...>]

Today is the original deadline for paper submissions. We are __extending__
this deadline_by one week, to __Sep 16, 2019, i.e. next Monday__.

Hello tcllib-devel, fyi ...

26th Annual Tcl/Tk Conference (Tcl'2019)
https://www.tcl-lang.org/community/tcl2019/

November 05 - 08, 2019
Crowne Plaza Houston River Oaks
2712 Southwest Freeway, 77098
Houston, Texas, USA

[ NEWS
  * Our keynote speaker is [Will Duquette](https://github.com/wduquette)
    talking about "Tcl, Rust, and the Death of Rube Goldberg"

  * [Submission is open](https://www.tcl-lang.org/community/tcl2019/cfp.html)

    We are at the original deadline for submissions. It has been extended
    by one week.

  * Registration is open. Please have a look at

    https://www.tcl-lang.org/community/tcl2019/register.html

  * The tutorials are known. See

    https://www.tcl-lang.org/community/tcl2019/tutorials.html
]

Important Dates:

Abstracts and proposals due   September 09, 2019  ** Extended by a week **
Notification to authors       September 16, 2019
WIP and BOF reservations open August 12, 2019
Registration opens            September 09, 2019     ** open already **
Author materials due          October 14, 2019
Tutorials Start               November 04, 2019
Conference starts             November 06, 2019

Email Contact:                tcl...@go...

Submission of Summaries

Tcl/Tk 2019 will be held in Houston, Texas, USA from November 05, 2019 to November 08, 2019.

The program committee is asking for papers and presentation proposals
from anyone using or developing with Tcl/Tk (and extensions). Past
conferences (Proceedings: https://www.tcl-lang.org/community/conferences.html)
have seen submissions covering a wide variety of topics including:

* Scientific and engineering applications
* Industrial controls
* Distributed applications and Network Managment
* Object oriented extensions to Tcl/Tk
* New widgets for Tk
* Simulation and application steering with Tcl/Tk
* Tcl/Tk-centric operating environments
* Tcl/Tk on small and embedded devices
* Medical applications and visualization
* Use of different programming paradigms in Tcl/Tk and proposals for new
  directions.
* New areas of exploration for the Tcl/Tk language

Submissions should consist of an abstract of about 100 words and a
summary of not more than two pages, and should be sent as plain text
to tcl...@go... no later than September 09, 2019. Authors of accepted
abstracts will have until October 14, 2019 to submit their final
paper for the inclusion in the conference proceedings. The proceedings
will be made available on digital media, so extra materials such as
presentation slides, code examples, code for extensions etc. are
encouraged.

Printed proceedings will be produced as an on-demand book at lulu.com
Online proceedings will appear via
	https://www.tcl-lang.org/community/conferences.html

The authors will have 30 minutes to present their paper at
the conference.

The program committee will review and evaluate papers according to the
following criteria:

* Quantity and quality of novel content
* Relevance and interest to the Tcl/Tk community
* Suitability of content for presentation at the conference

Proposals may report on commercial or non-commercial systems, but
those with only blatant marketing content will not be accepted.

Application and experience papers need to strike a balance between
background on the application domain and the relevance of Tcl/Tk to
the application. Application and experience papers should clearly
explain how the application or experience illustrates a novel use of
Tcl/Tk, and what lessons the Tcl/Tk community can derive from the
application or experience to apply to their own development efforts.

Papers accompanied by non-disclosure agreements will be returned to
the author(s) unread. All submissions are held in the highest
confidentiality prior to publication in the Proceedings, both as a
matter of policy and in accord with the U. S. Copyright Act of 1976.

The primary author for each accepted paper will receive registration
to the Technical Sessions portion of the conference at a reduced rate.

Other Forms of Participation

The program committee also welcomes proposals for panel discussions of
up to 90 minutes. Proposals should include a list of confirmed
panelists, a title and format, and a panel description with position
statements from each panelist. Panels should have no more than four
speakers, including the panel moderator, and should allow time for
substantial interaction with attendees. Panels are not presentations
of related research papers.

Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather
sessions (BOFs) are available on a first-come, first-served basis
starting in August 12, 2019. Specific instructions for reserving WIP
and BOF time slots will be provided in the registration information
available in August 12, 2019. Some WIP and BOF time slots will be held open
for on-site reservation. All attendees with an interesting work in
progress should consider reserving a WIP slot.

Registration Information

More information on the conference is available the conference Web
site (https://www.tcl-lang.org/community/tcl2019/) and will be
published on various Tcl/Tk-related information channels.

To keep in touch with news regarding the conference, subscribe to the
tcl...@go... list. See:
https://groups.google.com/forum/#!forum/tclconference for list
information, archive, and subscription.

To keep in touch with Tcl events in general, subscribe to the
tcl-announce list. See: https://code.activestate.com/lists/tcl-announce
for list information, archive, and subscription.

Conference Committee

   * Andreas Kupries
   * Arjen Markus    Deltares
   * Brian Griffin   Mentor - A Siemens Business
   * Gerald Lester   KnG Consulting LLC
   * Joe Mistachkin  Mistachkin Systems
   * Ronald Fox      CAEN Technologies
                     NSCL @ Michigan State University

Contact Information     tcl...@go...

Tcl'2019 would like to thank those who are sponsoring the conference:

   * FlightAware
   * Mentor - A Siemens Business
   * Noumena Corp

Re: [Tcllib-devel] Tcllib 1.20 Release - Candidate 1 - Please test

[Andreas K. <AKu...@su...>]

On Wed, 21 Aug 2019 11:17:07 +0000
"Pietro Cerutti" <ga...@ga...> wrote:

> On Aug 21 2019, 06:32 UTC, Andreas Kupries <aku...@sh...> wrote:
> >
> >I have started the work on Tcllib release 1.20.
> >
> >See
> >	https://core.tcl-lang.org/tcllib/timeline?r=tcllib-1-20-rc
> >
> >for the branch this work is happening on.
> >Please test this revision in your environments as well.  
> 
> Two "hook" and three "string" tests fail with 8.7 because of (I
> think) how it reports the name of namespaces ensemble commands.
> Everything else is fine with both 8.6 and 8.7. This is FreeBSD
> 12.0-RELEASE-p9 amd64.

Thanks. Looking at the results it certainly looks to be a core change
in the reporting of ensembles (full command getting reported now).

I guess I should add 8.7 into my lineup as well, despite being alpha
still, I believe.

That said, given the alpha-ness of 8.7 I am willing to let these issues
slide.

 
> ---- string-token-shell-1.0 start
> ==== string-token-shell-1.0 string token shell, wrong#args, not
> ---- Result was:
> wrong # args: should be
> "::string::token::shell ?-indices? ?-partial? ?--? text"

> ---- Result should have been (exact matching):
> wrong # args: should be
> "shell ?-indices? ?-partial? ?--? text" ==== string-token-shell-1.0

> FAILED



-- 
Andreas Kupries
SUSE Software Canada ULC
Tcl'2019, Nov 5-8, Houston, TX, USA.
http://www.tcl.tk/community/tcl2019/

Re: [Tcllib-devel] Tcllib 1.20 Release - Candidate 1 - Please test

[Pietro C. <ga...@ga...>]

On Aug 21 2019, 06:32 UTC, Andreas Kupries <aku...@sh...> wrote:
>
>I have started the work on Tcllib release 1.20.
>
>See
>	https://core.tcl-lang.org/tcllib/timeline?r=tcllib-1-20-rc
>
>for the branch this work is happening on.
>
>It passed the testsuite for me:
>
>	Platform: Linux amd64
>	Core:	  8.4.20, 8.5.19, 8.6.9
>	With:	  tcllibc
>
>Please test this revision in your environments as well.

Two "hook" and three "string" tests fail with 8.7 because of (I think) 
how it reports the name of namespaces ensemble commands.  Everything 
else is fine with both 8.6 and 8.7. This is FreeBSD 12.0-RELEASE-p9 
amd64.

---- errorcommand-1.2 start


==== errorcommand-1.2 error with -errorcommand set FAILED
==== Contents of test case:

    hook configure -errorcommand ErrorCommand

    hook bind S1 <H1> O1 {error "simulated error"}
    hook call S1 <H1>
    GetError

---- Result was:
{{S1 <H1> {} O1} {simulated error} {-code 1 -level 0 -errorstack {INNER {error {simulated error}} UP 1 CALL {::hook::call S1 <H1>}} -errorcode NONE}}
---- Result should have been (exact matching):
{{S1 <H1> {} O1} {simulated error} {-code 1 -level 0 -errorstack {INNER {error {simulated error}} UP 1 CALL {call S1 <H1>}} -errorcode NONE}}
==== errorcommand-1.2 FAILED

---- errorcommand-1.3 start


==== errorcommand-1.3 handled errors don't break sequence of calls FAILED
==== Contents of test case:

    hook configure -errorcommand ErrorCommand

    TestBind  S1 <H1> O1
    hook bind S1 <H1> O2 {error "simulated error"}
    TestBind  S1 <H1> O3
    hook call S1 <H1>
    list [GetCalls] [GetError]

---- Result was:
{{S1 <H1> O1 {}} {S1 <H1> O3 {}}} {{{S1 <H1> {} O2} {simulated error} {-code 1 -level 0 -errorstack {INNER {error {simulated error}} UP 1 CALL {::hook::call S1 <H1>}} -errorcode NONE}}}
---- Result should have been (exact matching):
{{S1 <H1> O1 {}} {S1 <H1> O3 {}}} {{{S1 <H1> {} O2} {simulated error} {-code 1 -level 0 -errorstack {INNER {error {simulated error}} UP 1 CALL {call S1 <H1>}} -errorcode NONE}}}
==== errorcommand-1.3 FAILED

---- string-token-shell-1.0 start


==== string-token-shell-1.0 string token shell, wrong#args, not enough FAILED
==== Contents of test case:

    string token shell

---- Result was:
wrong # args: should be "::string::token::shell ?-indices? ?-partial? ?--? text"
---- Result should have been (exact matching):
wrong # args: should be "shell ?-indices? ?-partial? ?--? text"
==== string-token-shell-1.0 FAILED

---- string-token-shell-1.1 start


==== string-token-shell-1.1 string token shell, wrong#args, too many FAILED
==== Contents of test case:

    string token shell T X

---- Result was:
wrong # args: should be "::string::token::shell ?-indices? ?-partial? ?--? text"
---- Result should have been (exact matching):
wrong # args: should be "shell ?-indices? ?-partial? ?--? text"
==== string-token-shell-1.1 FAILED

---- string-token-shell-1.2 start
++++ string-token-shell-1.2 PASSED
---- string-token-shell-1.3 start


==== string-token-shell-1.3 string token shell, wrong#args, too many FAILED
==== Contents of test case:

    string token shell -- T X

---- Result was:
wrong # args: should be "::string::token::shell ?-indices? ?-partial? ?--? text"
---- Result should have been (exact matching):
wrong # args: should be "shell ?-indices? ?-partial? ?--? text"
==== string-token-shell-1.3 FAILED




-- 
Pietro Cerutti

[Tcllib-devel] Tcllib 1.20 Release - Candidate 1 - Please test

[Andreas K. <aku...@sh...>]

I have started the work on Tcllib release 1.20.

See
	https://core.tcl-lang.org/tcllib/timeline?r=tcllib-1-20-rc

for the branch this work is happening on.

It passed the testsuite for me:

	Platform: Linux amd64
	Core:	  8.4.20, 8.5.19, 8.6.9
	With:	  tcllibc

Please test this revision in your environments as well.


My test controller:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#!/bin/bash
set -x

log=../ALL

clear
echo

rm -rf modules/tcllibc
rm -f                           ${log}.*
./sak.tcl critcl >              ${log}.critcl
time nice ./sak.tcl test run -l ${log} "$@"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-- 
See you,
	Andreas Kupries <aku...@sh...>
			<http://core.tcl.tk/akupries/>
	Developer @	SUSE Software Canada ULC
		  	<and...@su...>

Tcl'2019, Nov 5-8, Houston, TX, USA. http://www.tcl.tk/community/tcl2019/
-------------------------------------------------------------------------------

[Tcllib-devel] 3rd Call For Papers - 26th Annual Tcl/Tk Conference (Tcl'2019)

[<con...@tc...>]

Hello tcllib-devel, fyi ...

26th Annual Tcl/Tk Conference (Tcl'2019)
https://www.tcl-lang.org/community/tcl2019/

November 04 - 08, 2019
Crowne Plaza Houston River Oaks
2712 Southwest Freeway, 77098
Houston, Texas, USA

[ NEWS
  * Our keynote speaker is [Will Duquette](https://github.com/wduquette)
    talking about "Tcl, Rust, and the Death of Rube Goldberg"

  * [Submission is open](https://www.tcl-lang.org/community/tcl2019/cfp.html)

    It is 4 weeks to the deadline.

  * Registration is open. Please have a look at

    https://www.tcl-lang.org/community/tcl2019/register.html

  * The tutorials are known. See

    https://www.tcl-lang.org/community/tcl2019/tutorials.html
]

Important Dates:

Abstracts and proposals due   September 09, 2019
Notification to authors       September 16, 2019
WIP and BOF reservations open August 12, 2019     ** may change **
Registration opens            September 09, 2019     ** open already **
Author materials due          October 14, 2019
Tutorials Start               November 04, 2019
Conference starts             November 06, 2019

Email Contact:                tcl...@go...

Submission of Summaries

Tcl/Tk 2019 will be held in Houston, Texas, USA from November 04, 2019 to November 08, 2019.

The program committee is asking for papers and presentation proposals
from anyone using or developing with Tcl/Tk (and extensions). Past
conferences (Proceedings: https://www.tcl-lang.org/community/conferences.html)
have seen submissions covering a wide variety of topics including:

* Scientific and engineering applications
* Industrial controls
* Distributed applications and Network Managment
* Object oriented extensions to Tcl/Tk
* New widgets for Tk
* Simulation and application steering with Tcl/Tk
* Tcl/Tk-centric operating environments
* Tcl/Tk on small and embedded devices
* Medical applications and visualization
* Use of different programming paradigms in Tcl/Tk and proposals for new
  directions.
* New areas of exploration for the Tcl/Tk language

Submissions should consist of an abstract of about 100 words and a
summary of not more than two pages, and should be sent as plain text
to tcl...@go... no later than September 09, 2019. Authors of accepted
abstracts will have until October 14, 2019 to submit their final
paper for the inclusion in the conference proceedings. The proceedings
will be made available on digital media, so extra materials such as
presentation slides, code examples, code for extensions etc. are
encouraged.

Printed proceedings will be produced as an on-demand book at lulu.com
Online proceedings will appear via
	https://www.tcl-lang.org/community/conferences.html

The authors will have 30 minutes to present their paper at
the conference.

The program committee will review and evaluate papers according to the
following criteria:

* Quantity and quality of novel content
* Relevance and interest to the Tcl/Tk community
* Suitability of content for presentation at the conference

Proposals may report on commercial or non-commercial systems, but
those with only blatant marketing content will not be accepted.

Application and experience papers need to strike a balance between
background on the application domain and the relevance of Tcl/Tk to
the application. Application and experience papers should clearly
explain how the application or experience illustrates a novel use of
Tcl/Tk, and what lessons the Tcl/Tk community can derive from the
application or experience to apply to their own development efforts.

Papers accompanied by non-disclosure agreements will be returned to
the author(s) unread. All submissions are held in the highest
confidentiality prior to publication in the Proceedings, both as a
matter of policy and in accord with the U. S. Copyright Act of 1976.

The primary author for each accepted paper will receive registration
to the Technical Sessions portion of the conference at a reduced rate.

Other Forms of Participation

The program committee also welcomes proposals for panel discussions of
up to 90 minutes. Proposals should include a list of confirmed
panelists, a title and format, and a panel description with position
statements from each panelist. Panels should have no more than four
speakers, including the panel moderator, and should allow time for
substantial interaction with attendees. Panels are not presentations
of related research papers.

Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather
sessions (BOFs) are available on a first-come, first-served basis
starting in August 12, 2019. Specific instructions for reserving WIP
and BOF time slots will be provided in the registration information
available in August 12, 2019. Some WIP and BOF time slots will be held open
for on-site reservation. All attendees with an interesting work in
progress should consider reserving a WIP slot.

Registration Information

More information on the conference is available the conference Web
site (https://www.tcl-lang.org/community/tcl2019/) and will be
published on various Tcl/Tk-related information channels.

To keep in touch with news regarding the conference, subscribe to the
tcl...@go... list. See:
https://groups.google.com/forum/#!forum/tclconference for list
information, archive, and subscription.

To keep in touch with Tcl events in general, subscribe to the
tcl-announce list. See: https://code.activestate.com/lists/tcl-announce
for list information, archive, and subscription.

Conference Committee

   * Andreas Kupries
   * Arjen Markus    Deltares
   * Brian Griffin   Mentor - A Siemens Business
   * Gerald Lester   KnG Consulting LLC
   * Joe Mistachkin  Mistachkin Systems
   * Ronald Fox      CAEN Technologies
                     NSCL @ Michigan State University

Contact Information     tcl...@go...

Tcl'2019 would like to thank those who are sponsoring the conference:

   * FlightAware
   * Mentor - A Siemens Business
   * Noumena Corp

[Tcllib-devel] 2nd Call For Papers - 26th Annual Tcl/Tk Conference (Tcl'2019)

[<con...@tc...>]

Hello tcllib-devel, fyi ...

26th Annual Tcl/Tk Conference (Tcl'2019)
https://www.tcl-lang.org/community/tcl2019/

November 04 - 08, 2019
Crowne Plaza Houston River Oaks
2712 Southwest Freeway, 77098
Houston, Texas, USA

[ NEWS
 * Our keynote speaker is [Will Duquette](https://github.com/wduquette)
   talking about "Tcl, Rust, and the Death of Rube Goldberg"

 * [Submission is open](https://www.tcl-lang.org/community/tcl2019/cfp.html)
]

Important Dates:

Abstracts and proposals due   September 09, 2019
Notification to authors       September 16, 2019
WIP and BOF reservations open August 12, 2019     ** may change **
Registration opens            September 09, 2019     ** may change **
Author materials due          October 14, 2019
Tutorials Start               November 04, 2019
Conference starts             November 06, 2019

Email Contact:                tcl...@go...

Submission of Summaries

Tcl/Tk 2019 will be held in Houston, Texas, USA from November 04, 2019 to November 08, 2019.

The program committee is asking for papers and presentation proposals
from anyone using or developing with Tcl/Tk (and extensions). Past
conferences (Proceedings: https://www.tcl-lang.org/community/conferences.html)
have seen submissions covering a wide variety of topics including:

* Scientific and engineering applications
* Industrial controls
* Distributed applications and Network Managment
* Object oriented extensions to Tcl/Tk
* New widgets for Tk
* Simulation and application steering with Tcl/Tk
* Tcl/Tk-centric operating environments
* Tcl/Tk on small and embedded devices
* Medical applications and visualization
* Use of different programming paradigms in Tcl/Tk and proposals for new
  directions.
* New areas of exploration for the Tcl/Tk language

Submissions should consist of an abstract of about 100 words and a
summary of not more than two pages, and should be sent as plain text
to tcl...@go... no later than September 09, 2019. Authors of accepted
abstracts will have until October 14, 2019 to submit their final
paper for the inclusion in the conference proceedings. The proceedings
will be made available on digital media, so extra materials such as
presentation slides, code examples, code for extensions etc. are
encouraged.

Printed proceedings will be produced as an on-demand book at lulu.com
Online proceedings will appear via
	https://www.tcl-lang.org/community/conferences.html

The authors will have 30 minutes to present their paper at
the conference.

The program committee will review and evaluate papers according to the
following criteria:

* Quantity and quality of novel content
* Relevance and interest to the Tcl/Tk community
* Suitability of content for presentation at the conference

Proposals may report on commercial or non-commercial systems, but
those with only blatant marketing content will not be accepted.

Application and experience papers need to strike a balance between
background on the application domain and the relevance of Tcl/Tk to
the application. Application and experience papers should clearly
explain how the application or experience illustrates a novel use of
Tcl/Tk, and what lessons the Tcl/Tk community can derive from the
application or experience to apply to their own development efforts.

Papers accompanied by non-disclosure agreements will be returned to
the author(s) unread. All submissions are held in the highest
confidentiality prior to publication in the Proceedings, both as a
matter of policy and in accord with the U. S. Copyright Act of 1976.

The primary author for each accepted paper will receive registration
to the Technical Sessions portion of the conference at a reduced rate.

Other Forms of Participation

The program committee also welcomes proposals for panel discussions of
up to 90 minutes. Proposals should include a list of confirmed
panelists, a title and format, and a panel description with position
statements from each panelist. Panels should have no more than four
speakers, including the panel moderator, and should allow time for
substantial interaction with attendees. Panels are not presentations
of related research papers.

Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather
sessions (BOFs) are available on a first-come, first-served basis
starting in August 12, 2019. Specific instructions for reserving WIP
and BOF time slots will be provided in the registration information
available in August 12, 2019. Some WIP and BOF time slots will be held open
for on-site reservation. All attendees with an interesting work in
progress should consider reserving a WIP slot.

Registration Information

More information on the conference is available the conference Web
site (https://www.tcl-lang.org/community/tcl2019/) and will be
published on various Tcl/Tk-related information channels.

To keep in touch with news regarding the conference, subscribe to the
tcl...@go... list. See:
https://groups.google.com/forum/#!forum/tclconference for list
information, archive, and subscription.

To keep in touch with Tcl events in general, subscribe to the
tcl-announce list. See: https://code.activestate.com/lists/tcl-announce
for list information, archive, and subscription.

Conference Committee

   * Andreas Kupries
   * Arjen Markus    Deltares
   * Brian Griffin   Mentor - A Siemens Business
   * Gerald Lester   KnG Consulting LLC
   * Joe Mistachkin  Mistachkin Systems
   * Ronald Fox      CAEN Technologies
                     NSCL @ Michigan State University

Contact Information     tcl...@go...

Tcl'2019 would like to thank those who are sponsoring the conference:

   * FlightAware
   * Mentor - A Siemens Business
   * Noumena Corp

[Tcllib-devel] 1st Call For Papers - 26th Annual Tcl/Tk Conference (Tcl'2019)

[<con...@tc...>]

Hello tcllib-devel, fyi ...

26th Annual Tcl/Tk Conference (Tcl'2019)
https://www.tcl-lang.org/community/tcl2019/

November 04 - 08, 2019
Crowne Plaza Houston River Oaks
2712 Southwest Freeway, 77098
Houston, Texas, USA

[ NEWS
 * [Submission is open](https://www.tcl-lang.org/community/tcl2019/cfp.html)
]

Important Dates:

Abstracts and proposals due   September 09, 2019
Notification to authors       September 16, 2019
WIP and BOF reservations open August 12, 2019     ** may change **
Registration opens            September 09, 2019     ** may change **
Author materials due          October 14, 2019
Tutorials Start               November 04, 2019
Conference starts             November 06, 2019

Email Contact:                tcl...@go...

Submission of Summaries

Tcl/Tk 2019 will be held in Houston, Texas, USA from November 04, 2019 to November 08, 2019.

The program committee is asking for papers and presentation proposals
from anyone using or developing with Tcl/Tk (and extensions). Past
conferences (Proceedings: https://www.tcl-lang.org/community/conferences.html)
have seen submissions covering a wide variety of topics including:

* Scientific and engineering applications
* Industrial controls
* Distributed applications and Network Managment
* Object oriented extensions to Tcl/Tk
* New widgets for Tk
* Simulation and application steering with Tcl/Tk
* Tcl/Tk-centric operating environments
* Tcl/Tk on small and embedded devices
* Medical applications and visualization
* Use of different programming paradigms in Tcl/Tk and proposals for new
  directions.
* New areas of exploration for the Tcl/Tk language

Submissions should consist of an abstract of about 100 words and a
summary of not more than two pages, and should be sent as plain text
to tcl...@go... no later than September 09, 2019. Authors of accepted
abstracts will have until October 14, 2019 to submit their final
paper for the inclusion in the conference proceedings. The proceedings
will be made available on digital media, so extra materials such as
presentation slides, code examples, code for extensions etc. are
encouraged.

Printed proceedings will be produced as an on-demand book at lulu.com
Online proceedings will appear via
	https://www.tcl-lang.org/community/conferences.html

The authors will have 30 minutes to present their paper at
the conference.

The program committee will review and evaluate papers according to the
following criteria:

* Quantity and quality of novel content
* Relevance and interest to the Tcl/Tk community
* Suitability of content for presentation at the conference

Proposals may report on commercial or non-commercial systems, but
those with only blatant marketing content will not be accepted.

Application and experience papers need to strike a balance between
background on the application domain and the relevance of Tcl/Tk to
the application. Application and experience papers should clearly
explain how the application or experience illustrates a novel use of
Tcl/Tk, and what lessons the Tcl/Tk community can derive from the
application or experience to apply to their own development efforts.

Papers accompanied by non-disclosure agreements will be returned to
the author(s) unread. All submissions are held in the highest
confidentiality prior to publication in the Proceedings, both as a
matter of policy and in accord with the U. S. Copyright Act of 1976.

The primary author for each accepted paper will receive registration
to the Technical Sessions portion of the conference at a reduced rate.

Other Forms of Participation

The program committee also welcomes proposals for panel discussions of
up to 90 minutes. Proposals should include a list of confirmed
panelists, a title and format, and a panel description with position
statements from each panelist. Panels should have no more than four
speakers, including the panel moderator, and should allow time for
substantial interaction with attendees. Panels are not presentations
of related research papers.

Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather
sessions (BOFs) are available on a first-come, first-served basis
starting in August 12, 2019. Specific instructions for reserving WIP
and BOF time slots will be provided in the registration information
available in August 12, 2019. Some WIP and BOF time slots will be held open
for on-site reservation. All attendees with an interesting work in
progress should consider reserving a WIP slot.

Registration Information

More information on the conference is available the conference Web
site (https://www.tcl-lang.org/community/tcl2019/) and will be
published on various Tcl/Tk-related information channels.

To keep in touch with news regarding the conference, subscribe to the
tcl...@go... list. See:
https://groups.google.com/forum/#!forum/tclconference for list
information, archive, and subscription.

To keep in touch with Tcl events in general, subscribe to the
tcl-announce list. See: https://code.activestate.com/lists/tcl-announce
for list information, archive, and subscription.

Conference Committee

   * Andreas Kupries
   * Arjen Markus    Deltares
   * Brian Griffin   Mentor - A Siemens Business
   * Gerald Lester   KnG Consulting LLC
   * Joe Mistachkin  Mistachkin Systems
   * Ronald Fox      CAEN Technologies
                     NSCL @ Michigan State University

Contact Information     tcl...@go...

Tcl'2019 would like to thank those who are sponsoring the conference:

   * FlightAware
   * Mentor - A Siemens Business
   * Noumena Corp

Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

[Arjen M. <Arj...@de...>]

HI Andreas,

-----Original Message-----
From: Andreas Kupries <and...@su...>
Sent: 17 April 2019 18:36
To: Arjen Markus <Arj...@de...>
Cc: tcl...@li...
Subject: Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

On Wed, 17 Apr 2019 06:41:08 +0000
Arjen Markus <Arj...@de...> wrote:


> - In the section "Generate documentation for al modules" you may add
> that the tool updates the documentation, not simply generates
> everything

I suspect that you are confusing the `doc` method here with `localdoc`.

The latter is used to update the embedded and installation documentation. As such it generates all the docs multiple times (html, nroff, md), and updates the directories `embedded` and `idoc`.

While the `doc` command as specified generates the all docs, it only generates the specified format, and places it into a `doc` directory which has nothing to do with the embedded nor installations docs/directories.

>>AM: Ah, thanks for that clarification. Now I will go and read/comment on other pages.

Regards,

Arjen
DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.

Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

[Andreas K. <and...@su...>]

On Wed, 17 Apr 2019 06:41:08 +0000
Arjen Markus <Arj...@de...> wrote:

> Hi Andreas,
> 
> I have several small remarks on the Tcl Library Source Code page:
> - Typo: ramafications should be ramification

Fixed

> - In the section Trunk: "and this exactly" should be "and this is
> exactly"

Fixed

> - In the section "Generate documentation for al modules" you may add
> that the tool updates the documentation, not simply generates
> everything

I suspect that you are confusing the `doc` method here with `localdoc`.

The latter is used to update the embedded and installation
documentation. As such it generates all the docs multiple times (html,
nroff, md), and updates the directories `embedded` and `idoc`.

While the `doc` command as specified generates the all docs, it only
generates the specified format, and places it into a `doc` directory
which has nothing to do with the embedded nor installations
docs/directories.

> - In the section Notes on Writing A Testsuite: "throws an
> understandable error. Instead of" should be "throws an understandable
> error, instead of"

Fixed

> 
> As for testsuites, I was impressed by this article,
> https://www.researchgate.net/publication/298896236, that, admittedly,
> is geared to a particular numerical algorithm but shows that even
> simple-looking algorithms can lead to an incredible number of test
> cases.

Added the reference

Committed and pushed fixes.

-- 
Andreas Kupries
SUSE Software Canada ULC
EuroTcl 2019, Jun 29-30, Nuernberg/DE, http://eurotcl.eu/
Tcl'2019, Nov 4-8, Houston, TX, USA.
http://www.tcl.tk/community/tcl2019/

Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

[Andreas K. <and...@su...>]

On Wed, 17 Apr 2019 01:13:11 -0500
Andy Goth <and...@gm...> wrote:

> I found another formatting issue in the new markdown related to
> complex nested lists.


 
> https://core.tcl.tk/tcllib/doc/trunk/embedded/md/tcllib/files/modules/doctools/doctools_lang_cmdref.md#26
> 
> Scroll down to the following two paragraphs sandwiched between
> bulleted lists.
> 
> "Additionally the following names are recognized as shortcuts for some
> of the regular types:"
> 
> "At last the following names are still recognized for backward
> compatibility, but are otherwise considered to be deprecated."
> 
> The first list item (args and arg, respectively) of each list is not
> displayed correctly.
> 
> https://core.tcl.tk/tcllib/file?name=embedded/md/tcllib/files/modules/doctools/doctools_lang_cmdref.md&txt=1
> 
> Reviewing the generated markdown, I don't see any syntax errors.  This
> may be a fault in Fossil itself.  I'd cross-post to Fossil, but Fossil
> no longer has a mailing list.  Instead, it uses a forum:
> 
> https://fossil-scm.org/forum/forum

I confirm your findings, i.e. the .md file looks to have no syntax
errors, and the rendering of it is bad. Especially weird that
the first of the nested lists is not affected at all.

Only idea I have at the moment is invisible superfluous spaces causing
this ... Checked, no spaces around, thus out of ideas.

Ok. I will make a copy of this file later today and then try to reduce
it to something minimal still exhibiting the issue. When I have that I
will ping Richard.

Thanks for the report.

Seems that the docs of the entire Tcllib are a nice stress-tests for
both my generator, and fossil's renderer. And other renderers

If you look into examples rendered as block quotes (to allow for markup
inside the example) you will note that I use `&nbsp;` for leading
spaces to preserve indentation (somewhat, tab becomes space). I
am not replacing any of the internal spaces at all. Because if I do that
the pandoc parser seems to break down and misrender. Fossil maybe as
well.

-- 
Andreas Kupries
SUSE Software Canada ULC
EuroTcl 2019, Jun 29-30, Nuernberg/DE, http://eurotcl.eu/
Tcl'2019, Nov 4-8, Houston, TX, USA.
http://www.tcl.tk/community/tcl2019/

Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

[Arjen M. <Arj...@de...>]

Hi Andreas,

I have several small remarks on the Tcl Library Source Code page:
- Typo: ramafications should be ramification
- In the section Trunk: "and this exactly" should be "and this is exactly"
- In the section "Generate documentation for al modules" you may add that the tool updates the documentation, not simply generates everything
- In the section Notes on Writing A Testsuite: "throws an understandable error. Instead of" should be "throws an understandable error, instead of"

As for testsuites, I was impressed by this article, https://www.researchgate.net/publication/298896236, that, admittedly, is geared to a particular numerical algorithm but shows that even simple-looking algorithms can lead to an incredible number of test cases.

Regards,

Arjen


DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.

Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

[Andy G. <and...@gm...>]

I found another formatting issue in the new markdown related to complex
nested lists.

https://core.tcl.tk/tcllib/doc/trunk/embedded/md/tcllib/files/modules/doctools/doctools_lang_cmdref.md#26

Scroll down to the following two paragraphs sandwiched between bulleted
lists.

"Additionally the following names are recognized as shortcuts for some
of the regular types:"

"At last the following names are still recognized for backward
compatibility, but are otherwise considered to be deprecated."

The first list item (args and arg, respectively) of each list is not
displayed correctly.

https://core.tcl.tk/tcllib/file?name=embedded/md/tcllib/files/modules/doctools/doctools_lang_cmdref.md&txt=1

Reviewing the generated markdown, I don't see any syntax errors.  This
may be a fault in Fossil itself.  I'd cross-post to Fossil, but Fossil
no longer has a mailing list.  Instead, it uses a forum:

https://fossil-scm.org/forum/forum

-- 
Andy Goth | <andrew.m.goth/at/gmail/dot/com>

Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

[Andreas K. <aku...@sh...>]

> On 4/10/19 6:20 PM, Andreas Kupries wrote:
> > On Wed, 10 Apr 2019 18:03:10 -0500 Andy Goth <and...@gm...> wrote:

> I'm comparing the source with the generated markdown:
> 
> http://core.tcl.tk/tcllib/artifact?fn=modules/doctools/docidx_lang_intro.man&ci=c74461e613
> http://core.tcl.tk/tcllib/artifact?fn=embedded/md/tcllib/files/modules/doctools/doctools_lang_intro.md&ci=c74461e613&txt=1
> http://core.tcl.tk/tcllib/doc/c74461e613/embedded/md/tcllib/files/modules/doctools/doctools_lang_intro.md
> 
> But they seem to be quite different.  What am I missing?

docidx vs doctools

docidx_lang_intro.man
doctools_lang_intro.md
^^^^^^**

> Also, what is idoc?

i_nstallation doc_umentation.

Allows the installer.tcl to install the manpages or html by copying instead of 
computing everything on-the-fly on the destination machine.

> http://core.tcl.tk/tcllib/artifact?fn=idoc/www/tcllib/files/modules/doctools/docidx_lang_intro.html&ci=c74461e613

docidx again.

> At least for the section I quoted above, the idoc file matches the
> *.man source.

-- 
See you,
	Andreas Kupries <aku...@sh...>
			<http://core.tcl.tk/akupries/>
	Developer @	SUSE Software Canada ULC
		  	<and...@su...>

EuroTcl 2019, Jun 29-30, Nuernberg/DE, http://eurotcl.eu/
Tcl'2019, Nov 4-8, Houston, TX, USA. http://www.tcl.tk/community/tcl2019/
-------------------------------------------------------------------------------

Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

[Andy G. <and...@gm...>]

On 4/10/19 6:20 PM, Andreas Kupries wrote:
> On Wed, 10 Apr 2019 18:03:10 -0500 Andy Goth <and...@gm...> wrote:
>> Also, I'm curious why period is quoted with backslash: \.
> 
> Technically '.' is a special character in markdown, due to its use for
> ordered lists lead-in.

That makes sense.  Thank you.

I'm comparing the source with the generated markdown:

http://core.tcl.tk/tcllib/artifact?fn=modules/doctools/docidx_lang_intro.man&ci=c74461e613
http://core.tcl.tk/tcllib/artifact?fn=embedded/md/tcllib/files/modules/doctools/doctools_lang_intro.md&ci=c74461e613&txt=1
http://core.tcl.tk/tcllib/doc/c74461e613/embedded/md/tcllib/files/modules/doctools/doctools_lang_intro.md

But they seem to be quite different.  What am I missing?

The *.man source says:

[subsection Fundamentals]

While the [term {docidx markup language}] is quite similar to the
[term {doctools markup language}], in the broadest terms possible,
there is one key difference. An index consists essentially only of
markup commands, with no plain text interspersed between them, except
for whitespace.

The markdown says:

## <a name='subsection1'></a>Fundamentals

In the broadest terms possible the *doctools markup language* is 
LaTeX\-like,
instead of like SGML and similar languages\. A document written in this 
language
consists primarily of text, with markup commands embedded into it\.

Also, what is idoc?

http://core.tcl.tk/tcllib/artifact?fn=idoc/www/tcllib/files/modules/doctools/docidx_lang_intro.html&ci=c74461e613

At least for the section I quoted above, the idoc file matches the *.man
source.

-- 
Andy Goth | <andrew.m.goth/at/gmail/dot/com>

Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

[Andreas K. <and...@su...>]

On Wed, 10 Apr 2019 18:03:10 -0500
Andy Goth <and...@gm...> wrote:

> On 4/10/19 6:00 PM, Andy Goth wrote:
> > On 4/10/19 5:58 PM, Andreas Kupries wrote:  
> >> Fix is in, the examples should look much nicer now.  
> > 
> > Not quite.  Backslash at end of line still renders as two
> > backslashes. Look at the Fundamentals section here:
> > 
> > http://core.tcl.tk/tcllib/doc/trunk/embedded/md/tcllib/files/modules/doctools/doctoc_lang_intro.md 
> > 
> > http://core.tcl.tk/tcllib/file?name=embedded/md/tcllib/files/modules/doctools/doctoc_lang_intro.md&txt=1   

That double-backslash comes from the input file

   https://core.tcl.tk/tcllib/file?name=modules/doctools/doctoc_lang_intro.man&txt=1

A single backslash in the doctools input converts to space in what the
generator sees, due to Tcl subst rules.

Guess I need a bit more special handling for that, i.e. look for
double-\ followed by \n


> Also, I'm curious why period is quoted with backslash: \.

Technically '.' is a special character in markdown, due to its use for
ordered lists lead-in.

I based this on
	http://tech.saigonist.com/b/code/escaping-special-characters-markdown.html

Note also 
	https://spec.commonmark.org/0.28/#backslash-escapes
which I had not seen before. That is for inlines only, so not for
verbatim blocks.

-- 
Andreas Kupries
SUSE Software Canada ULC
EuroTcl 2019, Jun 29-30, Nuernberg/DE, http://eurotcl.eu/
Tcl'2019, Nov 4-8, Houston, TX, USA.
http://www.tcl.tk/community/tcl2019/

Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

[Andy G. <and...@gm...>]

On 4/10/19 6:00 PM, Andy Goth wrote:
> On 4/10/19 5:58 PM, Andreas Kupries wrote:
>> Fix is in, the examples should look much nicer now.
> 
> Not quite.  Backslash at end of line still renders as two backslashes.
> Look at the Fundamentals section here:
> 
> http://core.tcl.tk/tcllib/doc/trunk/embedded/md/tcllib/files/modules/doctools/doctoc_lang_intro.md 
> 
> http://core.tcl.tk/tcllib/file?name=embedded/md/tcllib/files/modules/doctools/doctoc_lang_intro.md&txt=1 

Also, I'm curious why period is quoted with backslash: \.

-- 
Andy Goth | <andrew.m.goth/at/gmail/dot/com>

Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

[Andy G. <and...@gm...>]

On 4/10/19 5:58 PM, Andreas Kupries wrote:
> Fix is in, the examples should look much nicer now.

Not quite.  Backslash at end of line still renders as two backslashes.
Look at the Fundamentals section here:

http://core.tcl.tk/tcllib/doc/trunk/embedded/md/tcllib/files/modules/doctools/doctoc_lang_intro.md

http://core.tcl.tk/tcllib/file?name=embedded/md/tcllib/files/modules/doctools/doctoc_lang_intro.md&txt=1

-- 
Andy Goth | <andrew.m.goth/at/gmail/dot/com>

Re: [Tcllib-devel] Tcllib - Dev- and other Guides - Looking For Feedback

[Andreas K. <and...@su...>]

On Wed, 10 Apr 2019 11:46:22 -0700
Andreas Kupries <and...@su...> wrote:

> On Wed, 10 Apr 2019 12:44:03 -0500
> Andy Goth <and...@gm...> wrote:
> 
> > On 4/9/19 10:46 PM, Andreas Kupries wrote:  
> > > If you are tracking Tcllib's
> > > [timeline](https://core.tcl.tk/tcllib/timeline) you might have
> > > seen that I am currently working in a branch [1] on a full set of
> > > guides for the various roles (user, installer/builder,
> > > developer/maintainer, release manager) associated with Tcllib.    

> > The big issue I see is extraneous backslashes in verbatim code
> > blocks, those being lines of text that begin with at least four
> > spaces.  
> 
> Yes. Arjen noted the same. I confirmed that pandoc does not like it
> either. I am currently working on that. Clearly I am overquoting
> the special characters. They are not special in the verbatim block and
> thus should not be quoted when I emit MD.

Fix is in, the examples should look much nicer now.

-- 
Andreas Kupries
SUSE Software Canada ULC
EuroTcl 2019, Jun 29-30, Nuernberg/DE, http://eurotcl.eu/
Tcl'2019, Nov 4-8, Houston, TX, USA.
http://www.tcl.tk/community/tcl2019/