[Chicken-users] First call for papers IFL 2014
Hello, Please, find below the first call for papers for IFL 2014. Please forward these to anyone you think may be interested. Apologies for any duplicates you may receive. best regards, Jurriaan Hage Publicity Chair of IFL --- CALL FOR PAPERS 26th SYMPOSIUM ON IMPLEMENTATION AND APPLICATION OF FUNCTIONAL LANGUAGES - IFL 2014 NORTHEASTERN UNIVERSITY/BOSTON, USA OCTOBER 1-3, 2014 http://ifl2014.github.io We are pleased to announce that the 26th edition of the IFL series will be held at Northeastern University in Boston, USA. The symposium will be held from 1st to 3rd of October 2014. Scope - The goal of the IFL symposia is to bring together researchers actively engaged in the implementation and application of functional and function-based programming languages. IFL 2014 will be a venue for researchers to present and discuss new ideas and concepts, work in progress, and publication-ripe results related to the implementation and application of functional languages and function-based programming. Following the IFL tradition, IFL 2014 will use a post-symposium review process to produce the formal proceedings. All participants of IFL 2014 are invited to submit either a draft paper or an extended abstract describing work to be presented at the symposium. At no time may work submitted to IFL be simultaneously submitted to other venues; submissions must adhere to ACM SIGPLAN's republication policy: http://www.sigplan.org/Resources/Policies/Republication The submissions will be screened by the program committee chair to make sure they are within the scope of IFL, and will appear in the draft proceedings distributed at the symposium. Submissions appearing in the draft proceedings are not peer-reviewed publications. Hence, publications that appear only in the draft proceedings do not count as publication for the ACM SIGPLAN republication policy. After the symposium, authors will be given the opportunity to incorporate the feedback from discussions at the symposium and will be invited to submit a revised full article for the formal review process. From the revised submissions, the program committee will select papers for the formal proceedings considering their correctness, novelty, originality, relevance, significance, and clarity. Submission Details -- Submission deadline draft papers: September 1 Notification of acceptance for presentation: September 5 Early registration deadline: September 10 Late registration deadline:September 17 Submission deadline for pre-symposium proceedings: September 24 26th IFL Symposium:October 1-3 Submission deadline for post-symposium proceedings:December 15 Notification of acceptance for post-symposium proceedings: January 31 2015 Camera-ready version for post-symposium proceedings: March15 2015 Prospective authors are encouraged to submit papers or extended abstracts to be published in the draft proceedings and to present them at the symposium. All contributions must be written in English. Papers must adhere to the standard ACM two columns conference format. For the pre-symposium proceedings we adopt a 'weak' page limit of 12 pages. For the post-symposium proceedings the page limit of 12 pages is firm. A suitable document template for LaTeX can be found at: http://www.acm.org/sigs/sigplan/authorInformation.htm Topics -- IFL welcomes submissions describing practical and theoretical work as well as submissions describing applications and tools in the context of functional programming. If you are not sure whether your work is appropriate for IFL 2014, please contact the PC chair at sa...@cs.indiana.edu. Topics of interest include, but are not limited to: - language concepts - type systems, type checking, type inferencing - compilation techniques - staged compilation - run-time function specialization - run-time code generation - partial evaluation - (abstract) interpretation - metaprogramming - generic programming - automatic program generation - array processing - concurrent/parallel programming - concurrent/parallel program execution - embedded systems - web applications - (embedded) domain specific languages - security - novel memory management techniques - run-time profiling performance measurements - debugging and tracing - virtual/abstract machine architectures - validation, verification of functional programs - tools and programming techniques - (industrial) applications Peter Landin Prize -- The Peter Landin Prize is awarded to the best paper presented at the symposium every year. The honoured article is selected by the program committee based on the submissions received for the formal review process. The prize carries a cash award equivalent to 150 Euros. Programme
Re: [Chicken-users] [ANN] New egg: glls
Hi, I'm pleased to announce glls Wow! Nice. :-) Good work. Regards, @ndy -- andy...@ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] New egg: physics
I would like to announce my first egg: physics. It is a more high-level wrapper to the brilliant Chipmunk2D physics library. Some highlights include: - The possibility of passing regular Chicken functions as callbacks. - Using regular Chicken objects as user data. - Garbage collection. - The possibility of optionally using 'map' instead of Chipmunk's iterator functions. Things left to do are: - More testing and adding some unit tests. - Finishing the documentation and adding some examples. If you want to take a look, the source can be found at: https://github.com/pluizer/chicken-physics https://github.com/pluizer/chicken-physics A more low-level wrapper to Chipmunk is required and can be found at: https://github.com/pluizer/chicken-chipmunk https://github.com/pluizer/chicken-chipmunk The documentation can be found at: https://wiki.call-cc.org/eggref/4/physics https://wiki.call-cc.org/eggref/4/physics As this is my first egg I might have done things wrongly or suboptimal, any pointers are welcome. thanks, Plui(j)zer (I'm trying to get rid of that j) ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] [ANN] New egg: glls
Great work, Alex! You beat me to it ;) Really looking forward to play around with this! It will be really interesting to see what dynamic shaders can do for games or other visually intensive application. K. On May 15, 2014 1:48 PM, Andy Bennett andy...@ashurst.eu.org wrote: Hi, I'm pleased to announce glls Wow! Nice. :-) Good work. Regards, @ndy -- andy...@ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] New egg: physics
Richard writes: I would like to announce my first egg: physics. It is a more high-level wrapper to the brilliant Chipmunk2D physics library. Some highlights include: - The possibility of passing regular Chicken functions as callbacks. - Using regular Chicken objects as user data. - Garbage collection. - The possibility of optionally using 'map' instead of Chipmunk's iterator functions. Things left to do are: - More testing and adding some unit tests. - Finishing the documentation and adding some examples. If you want to take a look, the source can be found at: https://github.com/pluizer/chicken-physics https://github.com/pluizer/chicken-physics A more low-level wrapper to Chipmunk is required and can be found at: https://github.com/pluizer/chicken-chipmunk https://github.com/pluizer/chicken-chipmunk The documentation can be found at: https://wiki.call-cc.org/eggref/4/physics https://wiki.call-cc.org/eggref/4/physics As this is my first egg I might have done things wrongly or suboptimal, any pointers are welcome. thanks, Plui(j)zer (I'm trying to get rid of that j) ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users Looking good, Plui( )zer! Have you thought about releasing your egg as an Official Chicken Extension™? You’re most of the way there, and it makes it a lot easier for other Chicken users to install, as well as allows the egg to become a dependency for other eggs. Check out this page for instructions: http://wiki.call-cc.org/eggs%20tutorial It seems as though all you’ll need to do is amend your setup file to add a version, add a bit more information to the meta file, and add a release-info file. After that, just ask to have your egg added. On the subject of amending your setup file, you should think about using Chicken tools for your compilation rather than using a Makefile (in fact, this might be a requirement for being added to the Coop, I’m not sure). The example that’s in that wiki page I linked shows how this can be done. It will simplify things a fair amount. Additionally, since your physics.import.scm file is generated from physics.scm, there’s no real reason to have it in your repo. And of course, all this goes for your chicken-chipmunk repo as well. Not sure if you saw it (since it’s not in the egg index) but acorn might be of interest to you, since it tackles the same problem. From a cursory glance, it seems as though you have solved some things that it has not, though: https://github.com/kristianlm/acorn I look forward to trying your egg out! -- Alex ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] New egg: physics
Hi, On Thu, 15 May 2014 23:14:35 +0200 Richard plui...@freeshell.de wrote: I would like to announce my first egg: physics. It is a more high-level wrapper to the brilliant Chipmunk2D physics library. Some highlights include: - The possibility of passing regular Chicken functions as callbacks. - Using regular Chicken objects as user data. - Garbage collection. - The possibility of optionally using 'map' instead of Chipmunk's iterator functions. Things left to do are: - More testing and adding some unit tests. - Finishing the documentation and adding some examples. If you want to take a look, the source can be found at: https://github.com/pluizer/chicken-physics A more low-level wrapper to Chipmunk is required and can be found at: https://github.com/pluizer/chicken-chipmunk The documentation can be found at: https://wiki.call-cc.org/eggref/4/physics As this is my first egg I might have done things wrongly or suboptimal, any pointers are welcome. Very nice. Thanks for contributing to the CHICKEN coop. It's actually two eggs! Here are a couple of suggestions to improve your eggs: - you probably don't need the .import.scm files in the code repository. csc generates them - instead of relying on an external make, you can use the make egg (http://wiki.call-cc.org/egg/make -- just mentioning in case you don't know it). If you prefer using the external make, that is fine, although it may be inconvenient and will probably require some tweaking. For example, if I want to use a chicken installation whose bin dir is not in PATH, I guess make will invoke the wrong csc. - the .meta files should contain at least category and license - physics' .meta should declare chipmunk as dependency - a very hardcore nitpicking: source files usually don't need the execute flag. :-) Please, consider fixing the .meta files at least before we add them to the official coop. Best wishes. Mario -- http://parenteses.org/mario ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] New egg: physics
Hi,
On Thu, 15 May 2014 18:23:48 -0400 Alex Charlton alex.n.charl...@gmail.com
wrote:
Richard writes:
I would like to announce my first egg: physics. It is a more high-level
wrapper to the brilliant Chipmunk2D physics library.
Some highlights include:
- The possibility of passing regular Chicken functions as callbacks.
- Using regular Chicken objects as user data.
- Garbage collection.
- The possibility of optionally using 'map' instead of Chipmunk's
iterator functions.
Things left to do are:
- More testing and adding some unit tests.
- Finishing the documentation and adding some examples.
If you want to take a look, the source can be found at:
https://github.com/pluizer/chicken-physics
https://github.com/pluizer/chicken-physics
A more low-level wrapper to Chipmunk is required and can be found at:
https://github.com/pluizer/chicken-chipmunk
https://github.com/pluizer/chicken-chipmunk
The documentation can be found at:
https://wiki.call-cc.org/eggref/4/physics
https://wiki.call-cc.org/eggref/4/physics
As this is my first egg I might have done things wrongly or suboptimal,
any pointers are welcome.
thanks,
Plui(j)zer (I'm trying to get rid of that j)
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
Looking good, Plui( )zer!
Have you thought about releasing your egg as an Official Chicken
Extension™? You’re most of the way there, and it makes it a lot easier
for other Chicken users to install, as well as allows the egg to
become a dependency for other eggs. Check out this page for
instructions:
http://wiki.call-cc.org/eggs%20tutorial
It seems as though all you’ll need to do is amend your setup file to
add a version,
The versioning thing is a little (?) can of worms. Strictly speaking,
it is not necessary (i.e., it won't cause errors), as long as your egg
is properly tagged with versions in the source repository.
henrietta-cache [1] will fetch egg sources and save them in a directory
named after tags. henrietta [2] will provide the version information,
based on the directory named after the tag and _that_ is used by
chicken-install to write versions to .setup-info files that get
installed along with eggs. So, for eggs that are installed by
chicken-install when it gets eggs from the henrietta server, the version
is always available. However, for local installations (i.e., cd
egg-source-dir; chicken-install), egg versions will be set as unknown
if they are not specified in .setup files. chicken-setup is oblivious
to VCS tags and tag directories -- only henrietta-cache and henrietta
care about them.
I usually provide a version in .setup files to avoid getting my eggs'
versions as unknown when I locally install them. Another reason for
specifying versions in .setup files is that the lack of version
information in .setup files also affects salmonella [3], since it
separates the fetch and the install steps (to be able to report
status separately for each step). So, it ends up performing local
installation. If .setup files contain no version, salmonella will
report their versions as unknown.
However, versions in .setup files come at a cost: information
duplication. You have to keep the version information in .setup, in
.release-info _and_ the VCS tag in sync at release time. That is kinda
painful is usually the cause of version inconsistencies (henrietta-cache
and henrietta don't know about versions in .setup files).
[1] http://wiki.call-cc.org/egg/henrietta-cache
[2] http://wiki.call-cc.org/egg/henrietta
[3] http://wiki.call-cc.org/egg/salmonella
\end{funnily_named_eggs}
add a bit more information to the meta file, and add a
release-info file. After that, just ask to have your egg added.
Oh, yes. The .release-info!
On the subject of amending your setup file, you should think about
using Chicken tools for your compilation rather than using a Makefile
(in fact, this might be a requirement for being added to the Coop, I’m
not sure).
In fact it is not, but fiddling with make may cause problems for
people who have CHICKEN installed on non-standard locations and for
those who cross-compile eggs. Unless, of course, you carefully craft
your makefiles, which is quite some work. The stuff from setup-api
(those things you use in .setup files like, compile, install-extension
etc.) are hairy (the internals, I mean), but they work in the weirdest
scenarios, as far as I can tell.
The example that’s in that wiki page I linked shows how
this can be done. It will simplify things a fair amount. Additionally,
since your physics.import.scm file is generated from physics.scm,
there’s no real reason to have it in your repo.
#t
And of course, all this goes for your chicken-chipmunk repo as well.
Not sure if you saw it (since it’s not in the egg index) but acorn
might be of interest to you, since it tackles the same problem. From a
