[ANN] 2017: Final call for workshop, symposium, demo & poster submissions

[timmolderez]

 * 2017* : The Art, Science, and Engineering of Programming

   April 3-6, 2017, Brussels, Belgium
   http://2017.programming-conference.org


Final call for submissions to all co-located events at the  
2017 conference:

 - ELS 2017 - 10th European Lisp Symposium
 - Modularity 2017 Invited talks - International Symposium on Modularity
 - **Updated** ACM Student Research Competition /  2017 Posters
 - **NEW**  2017 Demos
 - **NEW** CoCoDo 2017 - Raincode Labs Compiler Coding Dojo
 - LASSY 2017 - 2nd Workshop on Live Adaptation of Software SYstems
 - **NEW** MiniPLoP 2017 - Mini Pattern Languages of Programs writers' 
workshop
 - **Updated** MOMO 2017 - 2nd Workshop on Modularity in Modelling
 - MoreVMs 2017 - 1st Workshop on Modern Language Runtimes, Ecosystems, and 
VMs
 - PASS 2017 - 1st Workshop on Programming Across the System Stack
 - PX 2017 - 2nd Workshop on Programming Experience
 - ProWeb 2017 - 1st Workshop on Programming Technology for the Future Web
 - Salon des Refusés 2017 - 1st edition of the Salon des Refusés workshop

All co-located events will take place during April 3-4 2017.
CFPs for each of these events are listed below. (apart from Modularity 
2017, which is invitation-based)




 *ELS 2017 - 10th European Lisp Symposium*

   Submissions: Mon 30 Jan 2017
   Notifications: Mon 27 Feb 2017
   Symposium date: Mon Apr 3 - Tue Apr 4 2017

   http://2017.programming-conference.org/track/els-2017


The purpose of the European Lisp Symposium is to provide a forum for the 
discussion and dissemination of all aspects of design, implementation and 
application of any of the Lisp and Lisp-inspired dialects, including Common 
Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, 
ECMAScript, Racket, SKILL, Hop and so on. We encourage everyone interested 
in Lisp to participate.

The 10th European Lisp Symposium invites high quality papers about novel 
research results, insights and lessons learned from practical applications 
and educational perspectives. We also encourage submissions about known 
ideas as long as they are presented in a new setting and/or in a highly 
elegant way.

Topics include but are not limited to:

* Context-, aspect-, domain-oriented and generative programming
* Macro-, reflective-, meta- and/or rule-based development approaches
* Language design and implementation
* Language integration, inter-operation and deployment
* Development methodologies, support and environments
* Educational approaches and perspectives
* Experience reports and case studies




 *ACM Student Research Competition /  2017 Posters*

   Submissions **extended** : Mon 30 Jan 2017

   http://2017.programming-conference.org/track/programming-posters


The ACM Student Research Competition (SRC), sponsored by Microsoft 
Research, offers a unique forum for ACM student members at the 
undergraduate and graduate levels to present their original research before 
a panel of judges and conference attendees. The SRC gives visibility to 
up-and-coming young researchers, and offers them an opportunity to discuss 
their research with experts in their field, get feedback, and to help 
sharpen communication and networking skills. ACM’s SRC program covers 
expenses up to $500 for all students invited to an SRC. See our website for 
requirements and further details.

Please note that, while the SRC involves a poster session, there also is a 
regular poster session that isn't part of a competition. Submissions for 
this regular session are due March 3rd.




 *‹Programming› 2017 Demos*

   Submissions: Fri 3 Mar 2017

   http://2017.programming-conference.org/track/programming-2017-Demos


Demonstrations will be selected on the basis of technical merit, relevance, 
and novelty of presentation at . They can include work in 
progress, commercial or in-house applications, proofs of concept, results 
of academic or industrial research, or any other innovative programming 
tools 

Re: component dependency cleanup problem

[joakim . tengstrand]

Hi there!

Another solution is to use the Micro Monolith Architecture to solve 
dependency problems
which also gets you a really awesome development experience!

https://medium.com/@joakimtengstrand/the-micro-monolith-architecture-d135d9cafbe#.z7gjrqoif

On Wednesday, January 18, 2017 at 3:28:24 PM UTC+1, Jochen wrote:
>
> Hi…
>
> playing around with Stuart Sierras component library I found some behavior 
> (code at end) that I find odd.
> M sample has just two components, data and compute, where data is injected 
> into compute. On start data associates a data map and on stop dissociates 
> it.
> compute uses a value from data's map to compute.
>
> What I found is that after system stop the started version of data is 
> still associated to compute, while the data component in SystemMap is 
> stopped. So, when do
>
>   (def my-system (make-my-system {:factor 2}))
>   (alter-var-root #'my-system component/start-system)
>   (alter-var-root #'my-system component/stop-system)
>   (my-compute (:mycomputecomp my-system) 16)  
>
> my-compute should (as data map is nil'ed on stop) crash but doesn't.
>
> Calling
>
>   (alter-var-root #'my-system component/stop-system)
>
> again fixes it and my-compute crashes as expected.
>
> Any ideas?
>
> Ciao
>
> …Jochen
>
> (ns foo.core
>   (:require [com.stuartsierra.component :as component]))
>
> (defrecord MyDataComponent [data]
>   component/Lifecycle
>   (start [this]
> (println "Starting MyDataComponent")
> (assoc this :data {:foo 42}))
>   (stop [this]
> (println "Stopping MyDataComponent")
> (dissoc this :data)))
>
> (defn my-data-component []
>   (->MyDataComponent nil))
>
> (defn mydatacomp-foo [mydatacomp]
>   (get-in mydatacomp [:data :foo]))
>
>
> (defrecord MyComputeComponent [factor mydatacomp]
>   component/Lifecycle
>   (start [this]
> (println "Starting MyComputeComponent")
> this)
>   (stop [this]
> (println "Stopping MyComputeComponent")
> this))
>
> (defn my-compute-component [factor]
>   (map->MyComputeComponent {:factor factor}))
>
> (defn my-compute [mycomputecomp offset]
>   (let [factor (:factor mycomputecomp)
> foo(mydatacomp-foo (:mydatacomp mycomputecomp))]
> (+ (* factor foo) offset)))
>
> (defn make-my-system [config-options]
>   (let [{:keys [factor]} config-options]
> (component/system-map
>   :mydatacomp (my-data-component)
>   :mycomputecomp (component/using
>(my-compute-component factor)
>[:mydatacomp]
>
>
> ;; running 
> 
> (comment
>   (def my-system (make-my-system {:factor 2}))
>   (alter-var-root #'my-system component/start-system)
>   (alter-var-root #'my-system component/stop-system)
>   (my-compute (:mycomputecomp my-system) 16)
>   )
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] pedestal-api 0.3.1

[Oliver Hine]

I have released a small update to pedestal-api 
, a library for building APIs on the 
pedestal webserver.

This release makes it compatible with pedestal 0.5.2, which contains a 
security fix for a vulnerability fixed in ring 0.5.1 


Cheers
Oliy

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.