Re: [Chicken-users] hahn/salmonella issues

[Evan Hanson]

Hi Heinz,

On 2019-02-05 16:09, lundi wrote:
> > $ cat file.scm | sed 's/^[ \t]+//' | grep -e "^;;;" | cut -b 5- > file.wiki
> 
> I considered writing documenting comments in Markdown and then pipe those
> through markdown-svnwiki, but I feel like there's little benefit over just
> writing comments directly in svnwiki syntax.
> 
> Obviously there's a lot of room for improvement here. For instance it would
> be great to have a way of automatically converting procedure definitions
> into (fn args) blocks.

I hesitate to mention this since I'm pretty sure I'm the only person who
uses it, so it hasn't really been battle-tested (and it's not really
documented either), but the schematic egg might do what you're looking for.

In particular, the `schematic-wiki' program will generate svnwiki tags
for commented (toplevel) procedure definitions, with each tag followed
by the comment. So, if you use svnwiki syntax for the comments, the
result could be copied into a wiki page without any changes:

# chicken-install schematic
$ schematic-wiki -c ";;;" < file.scm

There's also a program called `schematic-extract' that generates
S-expressions instead of text, which you could post-process somehow.
There are some details about the expression format here:

  https://git.foldling.org/schematic.git/tree/0.2.1/schematic-extract.1.md

These are also available as library procedures, but again that's totally
undocumented (the irony, I know)... Ping me if you end up using this and
I'll try to help.

All the best,

Evan

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] hahn/salmonella issues

[lundi]

To answer my own question regarding possible alternatives to hahn: I 
found that simply writing documentation to source with a special comment 
prefix and then extracting that with some shell voodoo will be closest 
to what I want.


My main gripe with hahn is that IDEs will commonly not recognize the @() 
docstrings as such, so they will cause a lot of visual clutter in the 
source. So instead I'll just extract comments starting with a triple 
semicolon and write those to a wiki file.



$ cat file.scm | sed 's/^[ \t]+//' | grep -e "^;;;" | cut -b 5- > file.wiki


I considered writing documenting comments in Markdown and then pipe 
those through markdown-svnwiki, but I feel like there's little benefit 
over just writing comments directly in svnwiki syntax.


Obviously there's a lot of room for improvement here. For instance it 
would be great to have a way of automatically converting procedure 
definitions into (fn args) blocks. Also, support for 
multi-line comments and extracting info from .meta files would be nice 
to have.


Would anybody be interested in having an egg that provides this sort of 
functionality? I'm under the impression that hardly anybody uses hahn so 
I imagine nobody would use this either.


Best wishes,
-Heinz

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Chicken-users] [TFP'19] first call for papers: Trends in Functional Programming 2019, 12-14 June 2019, Vancouver, BC, CA

[Peter Achten]

 ---
   C A L L  F O R  P A P E R S
 ---

  == TFP 2019 ==

  20th Symposium on Trends in Functional Programming
   12-14 June, 2019
  Vancouver, BC, CA
  https://www.tfp2019.org/index.html


== Important Dates ==

Submission Deadline    Thursday, March 28, 2019
Paper Notification Thursday, May 2, 2019
TFPIE  Tuesday, June 11, 2019
Symposium  Wednesday, June 12, 2019 – Friday, June 
14, 2019

Student Paper Feedback Friday June 21, 2019
Submission for Formal Review   Thursday, August 1, 2019
Notification of Acceptance Thursday, October 24, 2019
Camera Ready   Friday, November 29, 2019


The symposium on Trends in Functional Programming (TFP) is an
international forum for researchers with interests in all aspects of
functional programming, taking a broad view of current and future
trends in the area. It aspires to be a lively environment for
presenting the latest research results, and other contributions (see
below at scope).

Please be aware that TFP uses two distinct rounds of submissions (see
below at submission details).

TFP 2019 will be the main event of a pair of functional programming
events. TFP 2019 will be accompanied by the International Workshop on
Trends in Functional Programming in Education (TFPIE), which will take
place on June 11.


== Scope ==

The symposium recognizes that new trends may arise through various 
routes. As part of the Symposium's focus on trends we therefore identify 
the following five article categories. High-quality articles are 
solicited in any of these categories:


    Research Articles:
    Leading-edge, previously unpublished research work
    Position Articles:
    On what new trends should or should not be
    Project Articles:
    Descriptions of recently started new projects
    Evaluation Articles:
    What lessons can be drawn from a finished project
    Overview Articles:
    Summarizing work with respect to a trendy subject

Articles must be original and not simultaneously submitted for 
publication to any other forum. They may consider any aspect of 
functional programming: theoretical, implementation-oriented, or 
experience-oriented. Applications of functional programming techniques 
to other languages are also within the scope of the symposium.


Topics suitable for the symposium include, but are not limited to:

    Functional programming and multicore/manycore computing
    Functional programming in the cloud
    High performance functional computing
    Extra-functional (behavioural) properties of functional programs
    Dependently typed functional programming
    Validation and verification of functional programs
    Debugging and profiling for functional languages
    Functional programming in different application areas:
    security, mobility, telecommunications applications, embedded
    systems, global computing, grids, etc.
    Interoperability with imperative programming languages
    Novel memory management techniques
    Program analysis and transformation techniques
    Empirical performance studies
    Abstract/virtual machines and compilers for functional languages
    (Embedded) domain specific languages
    New implementation strategies
    Any new emerging trend in the functional programming area

If you are in doubt on whether your article is within the scope of TFP, 
please contact the TFP 2019 program chairs, William J. Bowman and Ron 
Garcia.



== Best Paper Awards ==

To reward excellent contributions, TFP awards a prize for the best paper
accepted for the formal proceedings.

TFP traditionally pays special attention to research students, 
acknowledging
that students are almost by definition part of new subject trends. A 
student
paper is one for which the authors state that the paper is mainly the 
work of
students, the students are listed as first authors, and a student would 
present

the paper. A prize for the best student paper is awarded each year.

In both cases, it is the PC of TFP that awards the prize. In case the best
paper happens to be a student paper, that paper will then receive both 
prizes.



== Instructions to Author ==

Papers must be submitted at:

    https://easychair.org/conferences/?conf=tfp2019

Authors of papers have the choice of having their contributions formally 
reviewed either before or after the Symposium.



== Pre-symposium formal review ==

Papers to be formally reviewed before the symposium should be submitted 
before an early deadline and receive their reviews and notification of 
acceptance for both presentation and publication before the symposium. A 
paper that has been rejected in this process may still be accepted for 
presentation at the symposium, but will not be 

Re: [Chicken-users] SaarCHICKEN Spring 2019 in Saarbrücken, Germany

[Moritz Heidkamp]

Fellow CHICKENeers,

I'm happy to announce that due to the collective effort of many of you
taking part in the poll (thanks!) we now have a date for the SaarCHICKEN
Spring meeting:

  April 4 - 9, 2019

I've updated the wiki page[1] accordingly. Of course, you may join for
as long or short as you like. I guess we should schedule the
presentations for Saturday, though, so that even people who don't want
to or can't take some days off will have a chance to attend them.

Note that you can still join even if you didn't participate in the date
poll. Just add yourself to the list of attendants and shoot me an
email.

Since the venue will be my apartment, I'm not going to disclose the
exact address in public but will send it to all attendants by email in
advance.

I'll take care of all facilities for the meeting (tables, seats, power
sockets, network, projector). Let me know if you need anything else or
have any other questions!

Moritz


[1]  
http://wiki.call-cc.org/event/saarchicken-spring-2019#saarchicken-spring-2019


___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users