Gambit-list
Discussions par mois
- ----- 2026 -----
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2025 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2024 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2023 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2022 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2021 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2020 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2019 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2018 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2017 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2016 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2015 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2014 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2013 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2012 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2011 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2010 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2009 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2008 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2007 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2006 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2005 -----
- décembre
- novembre
- octobre
- septembre
- août
- juillet
- juin
- mai
- avril
- mars
- février
- janvier
- ----- 2004 -----
- décembre
- novembre
- octobre
- 3043 discussions
Hi,
I tried to build gambit on my home mac mini (macOS Sierra, 10.12.2) first
with xcode/gcc using
./configure --enable-gcc-opts
--prefix=/Users/kashyap/Documents/dev/gambitInstall; make -j4
latest-release; ./configure --enable-single-host --enable-gcc-opts; make
-j4 from-scratch; make check
This resulted in
../gsc-boot -:~~bin=../bin,~~lib=../lib,~~include=../include -f -warnings
-c -check _t-c-2.scm
make: *** [_t-c-2.c] Segmentation fault: 11
I then installed gcc using brew and tried with CC=gcc-6 option ... this too
resulted in the same error. I tried running gdb (after all the certificate
drama), but was not able to get any more information ...
(gdb) r -:~~bin=../bin,~~lib=../lib,~~include=../include -f -warnings -c
-check _t-c-2.scm
Starting program: /Users/kashyap/Documents/dev/gambit/gsc-boot
-:~~bin=../bin,~~lib=../lib,~~include=../include -f -warnings -c -check
_t-c-2.scm
During startup program terminated with signal SIG113, Real-time event 113.
Am I missing a something here?
Regards,
Kashyap
2
9
I have some news concerning the multiple threaded version of Gambit with encouraging preliminary performance results for mutex based synchronization.
The test program starts N threads that each increment a counter a million times. The incrementation is in a critical section implemented with a global mutex. So this is a scenario where there is intense contention for a single mutex by all the threads. I wrote the program in Scheme and also wrote a C version using pthreads. The Scheme program and the results are attached below.
When the programs are run (on OS X) with more than one thread (I tried 1 to 7 threads on a 4 core machine), the Gambit program is up to 15x faster than the C program using pthreads. Not bad for a first experiment with *no* tuning of the implementation! I think Gambit is so much faster because suspending a thread, which happens frequently here, is very fast thanks to continuations.
Marc
(declare (standard-bindings) (extended-bindings) (fixnum) (not safe) (block))
(define count 0)
(define mut (make-mutex))
(define (body)
(let loop ((n 1000000))
(if (> n 0)
(begin
(mutex-lock! mut)
(set! count (+ count 1))
(mutex-unlock! mut)
(loop (- n 1))))))
(define (iota n)
(let loop ((i (- n 1)) (lst '()))
(if (>= i 0)
(loop (- i 1) (cons i lst))
lst)))
(define threads
(map (lambda (id) (thread-start! (make-thread body)))
(iota (##current-vm-processor-count))))
(map thread-join! threads)
(pp count)
% make
gsc -exe test1.scm
time ./test1 -:p1
1000000
0.08 real 0.08 user 0.00 sys
time ./test1 -:p2
2000000
0.33 real 0.33 user 0.00 sys
time ./test1 -:p4
4000000
0.82 real 0.91 user 0.06 sys
time ./test1 -:p7
7000000
1.55 real 2.21 user 0.31 sys
gcc -O pthread1.c -o test1-pthread
time ./test1-pthread 1
count=1000000
0.02 real 0.02 user 0.00 sys
time ./test1-pthread 2
count=2000000
5.49 real 0.56 user 5.42 sys
time ./test1-pthread 4
count=4000000
12.77 real 1.11 user 12.10 sys
time ./test1-pthread 7
count=7000000
22.71 real 2.32 user 21.25 sys
1
0
<Programming> 2017: Final call for workshop, symposium, demo & poster submissions
by Tim Molderez 20 Jan '17
by Tim Molderez 20 Jan '17
20 Jan '17
-----------------------------------------------------------------------
<Programming> 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 <Programming>
2017 conference:
- ELS 2017 - 10th European Lisp Symposium
- Modularity 2017 Invited talks - International Symposium on Modularity
- **Updated** ACM Student Research Competition / <Programming> 2017
Posters
- **NEW** <Programming> 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 / <Programming> 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 <Programming>. 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 or systems. We encourage authors of
accepted papers to co-located workshops and main conferences also submit
a demo proposal. We hope that this will give them the opportunity to
show their work in action, and increase the visibility of their results.
We suggest to cite the paper in the demo abstract.
****************************************************************
CoCoDo 2017 - Raincode Labs Compiler Coding Dojo
Coding dojo date: Tue 4 Apr 2017
https://cocodo.github.io
****************************************************************
CoCoDo is a coding dojo where you can enjoy an entire day of compiler
programming under gentle guidance of field experts.
Compiler construction comprises, but is not limited to, lexical
analysis, syntactic analysis, preprocessing, context handling, code
generation, code optimisation, virtual machines, interpreters, smell
detection, clone management, portability, migration, refactoring,
domain-specific language design, linking and loading, assembling and
disassembling, generics and reflection, numerous paradigms and so much more.
If you are interested in participating, please contact Vadim Zaytsev:
vadim(a)raincodelabs.com
******************************************************************
LASSY 2017 - 2nd Workshop on Live Adaptation of Software SYstems
Submissions: Fri 3 Feb 2017
Notifications: Fri 3 Mar 2017
Workshop date: Mon 3 Apr 2017
http://2017.programming-conference.org/track/LASSY-2017-papers
******************************************************************
When developing current-day software systems, their deployment and usage
environments should be considered carefully, in order to understand the
adaptations those systems might need to undergo to interact with other
systems and with their environment. Moreover, due to the portability,
mobility and increasingly evolutionary nature of software systems, such
adaptations should be enacted even while the system is running.
Developing such software systems can prove challenging, and many
seemingly different techniques to address this concern have been
proposed over the last couple of years.
The intention of the LASSY workshop is to congregate all topics relevant
to dynamic adaptation and run-time evolution of software systems,
ranging from a computer science perspective covering the domains of
programming languages, model-driven software development, software and
service composition, context-aware databases, software variability,
requirements engineering, UI adaptation and other domains, to a human
perspective covering sociological or ethical implications of dynamic
software systems. The workshop provides a space for discussion and
collaboration between researchers working on the problem of enabling
live adaptations to software systems, across the development stack.
Topics of Interest:
* Design and Implementation of Live Adaptive Software Systems
* Context-, aspect-, feature-, role- and agent-oriented programming
* Context representation and discovery
* Context-aware model-driven software development
* Context-aware data management
* Software variability and dynamic product lines
* Self-adaptive, self-explanatory systems
* Inconsistency management, verification, and validation
* Middleware and Runtime of Live Adaptive Software Systems
* Dynamic software evolution, upgrades and configuration
* Dynamic software and service composition mechanisms
* Dynamic software architecture and middleware approaches
* Dynamic user interface adaptation and multimodal user interfaces
* Impact and Assessment of Live Adaptive Software Systems
* User acceptance and usability issues
* Human, sociological, ethical and legal aspects
* Privacy and security aspects of dynamic adaptability
* Live adaptation in smart environments (e.g. smart rooms,
smart robot cells, smart factories, smart cities)
* Self-adaptation and emergence in SoS and CPSoS
**********************************************************************
MiniPLoP 2017 - Mini Pattern Languages of Programs writers' workshop
Workshop date: Mon 3 Apr 2017
http://2017.programming-conference.org/track/MiniPLoP-2017-papers
**********************************************************************
Software developers and those involved with programming have long
observed that certain patterns recur and endure across different
applications and systems. The growing interest in Design Patterns,
Architectural Patterns, Analysis Patterns, Pedagogical Patterns, Agile
Patterns, and so on, represents an effort to catalog and better
communicate knowledge, providing handbooks of proven solutions to common
problems.
The MiniPLoP writers' workshop brings together researchers, educators,
and practitioners whose interests span a remarkably broad range of
topics and who share an interest in exploring the power of the pattern
form. MiniPLoP invites you to add your expertise to the growing corpus
of patterns. MiniPLoP focuses on improving the expression of patterns.
You will have the opportunity to refine and extend your patterns or
pattern ideas with the help from knowledgeable and sympathetic fellow
pattern enthusiasts. You will also be able to discuss applications of
patterns in industry and academia. Techniques for Pattern Mining will
also be presented.
Highlights include group discussions on patterns, an introduction to
pattern writing, an international keynote, and the writers’ workshop.
This MiniPLoP at <Programming> 2017 has the goal to help beginners learn
more about the pattern community. If you have some patterns or pattern
ideas you would like to have brainstormed or workshopped, please contact
the organizers at: miniplop2017(a)hillside.net
****************************************************************
MOMO 2017 - 2nd Workshop on Modularity in Modelling
Abstract submissions (optional) **extended** : Sun Feb 5 2017
Paper submissions **extended** : Sun Feb 12 2017
Notifications: Wed Feb 22 2017
Workshop date: Mon 3 Apr 2017
http://www.momo2017.ece.mcgill.ca/cfp.htm
****************************************************************
Extending the time-honored practice of separation of concerns,
Model-Driven Engineering (MDE) promotes the use of separate models to
address the various concerns in the development of complex
software-intensive systems. The main objective is to choose the right
level of abstraction to modularize a concern, specify its properties and
reason about the system under development depending on stakeholder and
development needs. While some of these models can be defined with a
single modelling language, a variety of heterogeneous models and
languages are typically used in the various phases of software
development. Furthermore, Domain-Specific Modelling Languages designed
to address particular concerns are also increasingly used.
Despite the power of abstraction of modelling, models of real-world
problems and systems quickly grow to such an extent that managing the
complexity by using proper modularization techniques becomes necessary.
As a result, many (standard) modelling notations have been extended with
aspect-oriented mechanisms and advanced composition operators to support
advanced separation of concerns, to combine (possibly heterogeneous)
models modularizing different concerns, to execute an application based
on modularized models, and to reason over global properties of
modularized models.
The Second International Modularity in Modelling Workshop brings
together researchers and practitioners interested in the theoretical and
practical challenges resulting from applying modularity, advanced
separation of concerns, and advanced composition at the modelling level.
It is intended to provide a forum for presenting new ideas and
discussing the impact of the use of modularization in the context of MDE
at different levels of abstraction.
We are interested in submissions on all topics related to modularity and
modelling including but not limited to:
* Modularization Support in Modelling Languages and Tools
* Model Interfaces
* Homogeneous Model Composition Operators
* Heterogeneous Model Composition Operators
* Visualization of Modularized and Composed Models
* Effects of Using Modularization and Composition in Modelling
* On Verification and Validation
* On Reuse
* On the Model-Driven Software Development Process
(Requirements Engineering, Software Architecture, Software Design,
Implementation)
* On Maintenance
* Experience Reports / Empirical Evaluations of Applying
Modularization and Composition in Modelling
* Feature-Oriented, Aspect-Oriented and Concern-Oriented Modelling
* Modularization support and composition operators for specific
modelling notations
* Modelling essential characteristics of specific
(crosscutting) concerns
* Multi-View Modelling: avoiding inconsistencies, avoiding
Redundancies
* Support for Detecting and/or Resolution of Feature Interactions
* Domain-Specific Modelling
* Modularization for Domain-Specific Languages
* Composition for Domain-Specific Languages
* Domain-specific Aspect Models
******************************************************************************
MoreVMs 2017 - 1st Workshop on Modern Language Runtimes, Ecosystems,
and VMs
Submissions: Wed 15 Feb 2017
Notifications: Wed 1 Mar 2017
Workshop date: Mon 3 Apr 2017
http://2017.programming-conference.org/track/MoreVMs-2017-papers
******************************************************************************
The main goal of the workshop is to bring together both researchers and
practitioners and facilitate effective sharing of their respective
experiences and ideas on how languages and runtimes are utilized and
where they need to improve further. We welcome presentation proposals in
the form of extended abstracts discussing experiences, work-in-progress,
as well as future visions from the academic as well as industrial
perspective.
Relevant topics include, but are definitely not limited to, the following:
* Extensible VM design (compiler- or interpreter-based VMs)
* Reusable runtime components (e.g. interpreters, garbage
collectors, intermediate representations)
* Static and dynamic compiler techniques
* Techniques for compilation to high-level languages such as JavaScript
* Runtimes and mechanisms for interoperability between languages
* Tooling support (e.g. debugging, profiling, etc.)
* Programming language development environments and virtual machines
* Case studies of existing language implementations, virtual
machines, and runtime components (e.g. design choices, tradeoffs, etc.)
* Language implementation challenges and trade-offs (e.g.
performance, completeness, etc.)
* Surveys and applications usage reports to understand runtime
usage in the wild
* Surveys on frameworks and their impact on runtime usage
* New research ideas on how we want to build languages in the future
**************************************************************************
PASS 2017 - 1st Workshop on Programming Across the System Stack
Submissions: Mon 13 Feb 2017
Notifications: Mon 27 Feb 2017
Workshop date: Tue 4 Apr 2017
http://2017.programming-conference.org/track/PASS-2017#Call-for-Papers
**************************************************************************
The landscape of computation platforms has changed dramatically in
recent years. Emerging systems - such as wearable devices, smartphones,
unmanned aerial vehicles, Internet of things, cloud computing servers,
heterogeneous clusters, and data centers - pose a distinct set of
system-oriented challenges ranging from data throughput, energy
efficiency, security, real-time guarantees, to high performance. In the
meantime, code quality, such as modularity or extensibility, remains a
cornerstone in modern software engineering, bringing in crucial benefits
such as modular reasoning, program understanding, and collaborative
software development. Current methodologies and software development
technologies should be revised in order to produce software to meet
system-oriented goals, while preserving high internal code quality. The
role of the Software Engineer is essential, having to be aware of the
implications that each design, architecture and implementation decision
has on the application system ecosystem.
This workshop is driven by one fundamental question: How does internal
code quality interact with system-oriented goals? We welcome both
positive and negative responses to this question. An example of the
former would be modular reasoning systems specifically designed to
promote system-oriented goals, whereas an example of the latter would be
anti-patterns against system-oriented goals during software development.
Areas of interest include but are not limited to:
* Energy-aware software engineering (e.g. energy efficiency models,
energy efficiency as a quality attribute)
* Modularity support (e.g., programming language design,
development tools or verification) for applications in
resource-constrained or real-time systems
* Emerging platforms (e.g., Internet of Things and wearable devices)
* Security support (e.g., compositional information flow,
compositional program analysis)
* Software architecture for reusability and adaptability in systems
and their interactions with applications
* Empirical studies (patterns and anti-patterns) on the
relationship between internal code quality and system-oriented goals
* Software engineering techniques to balance the trade-off between
internal code quality and efficiency
* Memory bloats and long-tail performance problems across modular
boundaries
* Program optimization across modular boundaries
* Internal code quality in systems software
* Reasoning across applications, compilers, and virtual machines
****************************************************************
PX 2017 - 2nd Programming Experience Workshop
Submissions: Sat 4 Feb 2017
Notifications: Mon 27 Feb 2017
Workshop date: Mon 3 Apr 2017
http://programming-experience.org/px17
****************************************************************
Imagine a software development task: some sort of requirements and
specification including performance goals and perhaps a platform and
programming language. A group of developers head into a vast workroom.
In that room they discover they need to explore the domain and the
nature of potential solutions—they need exploratory programming.
The Programming Experience Workshop is about what happens in that room
when one or a couple of programmers sit down in front of computers and
produce code, especially when it’s exploratory programming. Do they
create text that is transformed into running behavior (the old way), or
do they operate on behavior directly (“liveness”); are they exploring
the live domain to understand the true nature of the requirements; are
they like authors creating new worlds; does visualization matter; is the
experience immediate, immersive, vivid and continuous; do fluency,
literacy, and learning matter; do they build tools, meta-tools; are they
creating languages to express new concepts quickly and easily; and
curiously, is joy relevant to the experience?
Correctness, performance, standard tools, foundations, and
text-as-program are important traditional research areas, but the
experience of programming and how to improve and evolve it are the focus
of this workshop, and in this edition we would like to focus on
exploratory programming.
The technical topics include:
* Exploratory programming
* Live programming
* Authoring
* Representation of active content
* Visualization
* Navigation
* Modularity mechanisms
* Immediacy
* Literacy
* Fluency
* Learning
* Tool building
* Language engineering
*************************************************************************
ProWeb 2017 - 1st Workshop on Programming Technology for the Future Web
Submissions: Wed 15 Feb 2017
Notifications: Wed 1 Mar 2017
Workshop date: Tue 4 Apr 2017
http://2017.programming-conference.org/track/proweb-2017-papers
*************************************************************************
Full-fledged web applications have become ubiquitous on desktop and
mobile devices alike. Whereas “responsive” web applications already
offered a more desktop-like experience, there is an increasing demand
for “rich” web applications (RIAs) that offer collaborative and even
off-line functionality —Google docs being the prototypical example. Long
gone are the days that web servers merely had to answer incoming HTTP
request with a block of static HTML. Today’s servers react to a
continuous stream of events coming from JavaScript applications that
have been pushed to clients. As a result, application logic and data is
increasingly distributed. Traditional dichotomies such as “client vs.
server” and “offline vs. online” are fading.
The 1st International Workshop on Programming Technology for the Future
Web, or ProWeb17, is a forum for researchers and practitioners to share
and discuss new technology for programming these and future evolutions
of the web. We welcome submissions introducing programming technology
(i.e., frameworks, libraries, programming languages, program analyses
and development tools) for implementing web applications and for
maintaining their quality over time, as well as experience reports about
the use of state-of-the-art programming technology.
Relevant topics include, but are not limited to:
* Quality on the new web: static and dynamic program analyses;
code, design test and process metrics; development and migration tools;
automated testing and test generation; contract systems, type systems,
and web service API conformance checking; …
* Hosting languages on the web: new runtimes; transpilation or
compilation to JavaScript, WebAssembly, asm.js, …
* Designing languages for the web: multi-tier (or tierless)
programming; reactive programming; frameworks for multi-tier or reactive
programming on the web; …
* Distributed data sharing, replication and consistency: cloud
types, CRDTs, eventual consistency, offline storage, peer-to-peer
communication, …
* Security on the web: client-side and server-side security
policies; policy enforcement; proxies and membranes; vulnerability
detection; dynamic patching, …
* Surveys and case studies using state-of-the-art web technology
(e.g., WebAssembly, WebSocket, LocalStorage, AppCache, ServiceWorkers,
Meteor, deepstream.io, Angular.js, React and React Native, Swarm.js,
Caja, TypeScript, Proxies, ClojureScript, Amber Smalltalk, Scala.js, …)
* Ideas on and experience reports about: how to reconcile the need
for quality with the need for agility on the web; how to master and
combine the myriad of tier-specific technologies required to develop a
web application, …
* Position statements on what the future of the web will look like
****************************************************************
Salon des Refusés 2017
Submissions: Wed 1 Feb 2017
Notifications: Fri 17 Feb 2017
Workshop date: Tue 4 Apr 2017
https://refuses.github.io
****************************************************************
Salon des Refusés (“exhibition of rejects”) was an 1863 exhibition of
artworks rejected from the official Paris Salon. The jury of Paris Salon
required near-photographic realism and classified works according to a
strict genre hierarchy. Paintings by many, later famous, modernists such
as Édouard Manet were rejected and appeared in what became known as the
Salon des Refusés. This workshop aims to be the programming language
research equivalent of Salon des Refusés. We provide a venue for
exploring new ideas and new ways of doing computer science.
Many interesting ideas about programming might struggle to find space in
the modern programming language research community, often because they
are difficult to evaluate using established evaluation methods (be it
proofs, measurements or controlled user studies). As a result, new ideas
are often seen as “unscientific”.
This workshop provides a venue where such interesting and
thought-provoking ideas can be exposed to critical evaluation.
Submissions that provoke interesting discussion among the program
committee members will be published together with an attributed review
that presents an alternative position, develops additional context or
summarizes discussion from the workshop. This means of engaging with
papers not just enables explorations of novel programming ideas, but
also encourages new ways of doing computer science.
Topics of interest
The scope of the workshop is determined more by the format of
submissions than by the specific area of programming language or
computer science research that we are interested in. We welcome
submissions in a format that makes it possible to think about
programming in a new way, including, but not limited to:
* Thought experiments – we believe that thought experiments,
analogies and illustrative metaphors can provide novel insights and
inspire fruitful programming language ideas.
* Experimentation – we find prejudices in favour of theory, as far
back as there is institutionalized science, but programming can often be
seen more as experimentation than as theorizing. We welcome interesting
experiments even if there is yet no overarching theory that explains why
they happened.
* Paradigms – all scientific work is rooted in a scientific
paradigm that frame what questions can be asked. We encourage
submissions that reflect on existing paradigms or explore alternative
scientific paradigms.
* Metaphors, myths and analogies – any description of formal,
mathematical, quantitative or even poetical nature still represents just
an analogy. We believe that fruitful ideas can be learned from less
common forms of analogies as well as from the predominant, formal and
mathematical ones.
* From jokes to science fiction – a story or an artistic
performance may explore ideas and spark conversations that provide
crucial inspiration for development of new computer science thinking.
1
0
Hi,
Looks like 90 minute scheme to C compiler does not work with new gambit -
all's well until code-gen. At code gen, it appears that extra round
brackets are emitted when we use new gambit. I am managing with 4.0 for now
- I've gone through the CPS conversion and closure conversion (the video
helped a lot). I am now going through code generation.
Sharing it just in case its a trivial something I need to do to get it
working with new gambit...
Regards,
Kashyap
4
4
A function (that really runs in Gambit):
(define (🍔 🍟)
(let ((🎃 <)(🎂 +)(🍣 -)(🍕 1)(🍆 2))
(if (🎃 🍟 🍆)
🍕
(🎂 (🍔 (🍣 🍟 🍆))
(🍔 (🍣 🍟 🍕))))))
Unfortunately, there is not yet a nachos emoji, or we could define
fibonachos:
http://www.gocomics.com/foxtrot/2009/02/08/
Brad
4
8
Thanks Marc,
I shall try with your suggested prefix.
For visual studio - here's what I did
1. Cloned a fresh repo
2. Unzipped vstudio.zip into the repo root
3. Opend the sln file
4. Removed lib/os.c and added lib/os_setup.c
5. Did a build - got 615 errors - mostly cannot open gambit.h
6. So I ran ./configure and retried - did not help
For msys2, I am afraid, I did not follow the instructions properly.
Regards,
Kashyap
Severity Code Description Project File Line Suppression State
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 8967
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 8973
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 8996
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 9002
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 9069
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 9075
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 9950
Error C2143 syntax error: missing ';' before '{' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 10012
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 10934
Error C2143 syntax error: missing ';' before '{' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 10985
Error C2143 syntax error: missing ';' before '{' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11035
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11214
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11219
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11259
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11288
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11377
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11393
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11440
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11623
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11668
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11916
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 11924
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12001
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12072
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12130
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12142
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12194
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12223
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12268
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12280
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12412
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12420
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12536
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12808
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12910
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12921
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12945
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12956
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12964
Error C2146 syntax error: missing ';' before identifier '___r0' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 12983
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 13005
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 13021
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 13505
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 13722
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 13728
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 14191
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 14219
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 14381
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 14410
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 14471
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 14822
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 14833
Error C2146 syntax error: missing ';' before identifier '___r1' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 14855
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 14867
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 14908
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15111
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15122
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15133
Error C2146 syntax error: missing ';' before identifier
'___L7__23__23_thread_2d_send' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15147
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15170
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15378
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15392
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15452
Error C2146 syntax error: missing ';' before identifier '___r0' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15459
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15464
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15510
Error C2146 syntax error: missing ';' before identifier '___r1' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15564
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15590
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15665
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15677
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15682
Error C2146 syntax error: missing ';' before identifier '___r1' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15757
Error C2146 syntax error: missing ';' before identifier
'___L17__23__23_mutex_2d_signal_2d_and_2d_condvar_2d_wait_21_' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15769
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15786
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15791
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15836
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15913
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15922
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 15933
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 16051
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 16127
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 16511
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 16517
Error C2065 '___RUNQUEUE': undeclared identifier lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19038
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19401
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19406
Error C2146 syntax error: missing ';' before identifier '___r1' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19421
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19437
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19442
Error C2146 syntax error: missing ';' before identifier '___r1' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19456
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19480
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19485
Error C2146 syntax error: missing ';' before identifier '___r1' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19495
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19521
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19526
Error C2146 syntax error: missing ';' before identifier '___r1' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19539
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19688
Error C2146 syntax error: missing ';' before identifier '___r1' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 19700
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 22582
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 22593
Error C2146 syntax error: missing ';' before identifier '___r1' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 22629
Error C1003 error count exceeds 100; stopping compilation lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_thread.c 22629
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_repl.c 23586
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_repl.c 23597
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_repl.c 23656
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_repl.c 23700
Error C2146 syntax error: missing ';' before identifier '___r1' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_repl.c 23712
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 19850
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 19862
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 19882
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 19894
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 19908
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 19925
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 19937
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 19956
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 19973
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 19985
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20023
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20035
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20109
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20120
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20129
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20139
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20151
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20209
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20226
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20238
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20259
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20271
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20308
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20351
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20362
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20382
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20394
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 20423
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 21612
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 21624
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 21643
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 21654
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 21663
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 21905
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 21917
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 21936
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 21947
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 21956
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 23164
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 23175
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 23233
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 23257
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 23261
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24007
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24018
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24027
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24093
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24104
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24110
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24227
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24239
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24259
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24272
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24285
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24299
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24316
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24328
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24347
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24379
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24390
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24425
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24439
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24450
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24465
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24477
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24489
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24509
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24521
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24550
Error C2146 syntax error: missing ';' before identifier
'___L97__23__23_make_2d_vector_2d_port' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24562
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24592
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24604
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24629
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24641
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24677
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24699
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24710
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24734
Error C2146 syntax error: missing ';' before identifier
'___L109__23__23_make_2d_vector_2d_port' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24746
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24773
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24785
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24819
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24831
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 24845
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 25961
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 25972
Error C2146 syntax error: missing ';' before identifier '___r3' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 26000
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 26024
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 26028
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 26803
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 26814
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 26823
Error C2146 syntax error: missing ';' before identifier '___r4' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 26889
Error C2143 syntax error: missing ';' before 'if' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 26900
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 26906
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 27027
Error C2143 syntax error: missing ';' before 'goto' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 27039
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 27059
Error C2146 syntax error: missing ';' before identifier '___r2' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 27072
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 27085
Error C2146 syntax error: missing ';' before identifier '___fp' lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 27099
Error C1003 error count exceeds 100; stopping compilation lib
c:\mingw\msys\1.0\home\ckk\gambit\lib\_io.c 27099
Error C1083 Cannot open include file: 'gambit-not408007.h': No such file or
directory gsi c:\mingw\msys\1.0\home\ckk\gambit\include\gambit.h 15
Error C1083 Cannot open include file: 'gambit-not408007.h': No such file or
directory gsc c:\mingw\msys\1.0\home\ckk\gambit\include\gambit.h 15
On Wed, Jan 18, 2017 at 3:57 PM, Marc Feeley <dr.marc.feeley(a)gmail.com>
wrote:
> Thanks for your feedback… but it shouldn’t be this complicated! For mingw
> you should use a --prefix like this
>
> --prefix=C:/MinGW/msys/1.0/GAMBITSCHEME
>
> to avoid moving the whole directory.
>
> For Visual Studio, there’s probably a file or two missing in the .sln
> project (I don’t keep it up to date… my guess is add “lib/os_setup.c” and
> remove “lib/os.c”).
>
> For msys2, did you get the sources from a clone of the github repository?
> If so, the instructions in INSTALL.txt should be followed precisely to
> bootstrap Gambit.
>
> Marc
>
> > On Jan 18, 2017, at 6:37 PM, C K Kashyap <ckkashyap(a)gmail.com> wrote:
> >
> > Hi all,
> >
> > I was able to get Gambit to build on windows - I tried initially with
> msys2 (hoping to build a 64bit version) - but failed -
> >
> > $ make install
> > making all in include
> > make[1]: Entering directory '/home/ckk/gambit/include'
> > make[1]: Leaving directory '/home/ckk/gambit/include'
> > making all in lib
> > make[1]: Entering directory '/home/ckk/gambit/lib'
> > ../gsc-boot -:~~bin=../bin,~~lib=../lib,~~include=../include -f -c
> -check -prelude "(##include \"header.scm\")" _repl.scm
> > make[1]: *** [makefile:167: _repl.c] Segmentation fault
> > make[1]: *** Deleting file '_repl.c'
> > make[1]: Leaving directory '/home/ckk/gambit/lib'
> > make: *** [makefile:417: all-recursive] Error 1
> >
> >
> > After that, I tried using VS 2015 (unzipped vstudio.zip -- opened the
> sln - but did not succeed)
> >
> > Eventually, I tried with mingw (from mingw.org) -
> >
> > ./configure; make -j4 latest-release ; ./configure
> --prefix=/GAMBITSCHEME --enable-single-host; make -j4 from-scratch
> > ; make check; make -j4 doc; make install
> >
> > The above resulted in GAMBITSCHEME getting created under / -> under
> C:\MinGW\msys\1.0 that is .... however I got this error -
> >
> > $ gsc -exe hello.scm
> > *** ERROR IN ##parameterize -- No such file or directory
> > (current-directory "\\GAMBITSCHEME\\bin\\")
> >
> >
> > So, I copied the whole GAMBITSCHEME director under C:\ and wala!!!
> things worked (I now have a working gambit compiler on my windows box -
> where I need to spend a lot of time). I am sharing this just in case anyone
> finds this useful. I am going to try to use the prebuilt 64 bit windows
> build (I had tried it earlier but had run into some issues)
> >
> >
> > Regards,
> > Kashyap
> >
> >
> >
> > _______________________________________________
> > Gambit-list mailing list
> > Gambit-list(a)iro.umontreal.ca
> > https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
>
>
3
5
Hi all,
I was able to get Gambit to build on windows - I tried initially with msys2
(hoping to build a 64bit version) - but failed -
$ make install
making all in include
make[1]: Entering directory '/home/ckk/gambit/include'
make[1]: Leaving directory '/home/ckk/gambit/include'
making all in lib
make[1]: Entering directory '/home/ckk/gambit/lib'
../gsc-boot -:~~bin=../bin,~~lib=../lib,~~include=../include -f -c -check
-prelude "(##include \"header.scm\")" _repl.scm
make[1]: *** [makefile:167: _repl.c] Segmentation fault
make[1]: *** Deleting file '_repl.c'
make[1]: Leaving directory '/home/ckk/gambit/lib'
make: *** [makefile:417: all-recursive] Error 1
After that, I tried using VS 2015 (unzipped vstudio.zip -- opened the sln -
but did not succeed)
Eventually, I tried with mingw (from mingw.org) -
./configure; make -j4 latest-release ; ./configure --prefix=/GAMBITSCHEME
--enable-single-host; make -j4 from-scratch
; make check; make -j4 doc; make install
The above resulted in GAMBITSCHEME getting created under / ->
under C:\MinGW\msys\1.0 that is .... however I got this error -
$ gsc -exe hello.scm
*** ERROR IN ##parameterize -- No such file or directory
(current-directory "\\GAMBITSCHEME\\bin\\")
So, I copied the whole GAMBITSCHEME director under C:\ and wala!!! things
worked (I now have a working gambit compiler on my windows box - where I
need to spend a lot of time). I am sharing this just in case anyone finds
this useful. I am going to try to use the prebuilt 64 bit windows build (I
had tried it earlier but had run into some issues)
Regards,
Kashyap
3
3
Hi,
I just realized that I am not getting any of the Gambit emails. Could
someone please ack this?
regards,
Kashyap
2
1
/************************************************************************************/
ACM Conference on Systems, Programming, Languages, and Applications:
Software for Humanity (SPLASH'17)
Vancouver, Canada
October 22-27, 2017
http://2017.splashcon.org <http://2017.splashcon.org/>
Sponsored by ACM SIGPLAN
/************************************************************************************/
CALL FOR CONTRIBUTIONS:
Workshops
/************************************************************************************/
## SPLASH Workshops
Following its long-standing tradition, SPLASH 2017 will host a variety of high-quality workshops, allowing their participants to meet and discuss research questions with peers, to mature new and exciting ideas, and to build up communities and start new collaborations. SPLASH workshops complement the main tracks of the conference and provide meetings in a smaller and more specialized setting. Workshops cultivate new ideas and concepts for the future, optionally recorded in formal proceedings.
## Call for Submissions:
We encourage proposals for workshops on any topic relevant to SPLASH. If there is a topic relevant to SPLASH that you feel passionate about, and you want to connect with others who have similar interests, you should consider submitting a proposal to organize a workshop! The exact format of the workshop can be defined by the proposal submitters, and we more than welcome new, and unconventional ideas for workshop formats. The following suggestions may serve as a starting point:
- Mini-conferences provide their participants the possibility to present their work to other domain experts. The smaller and more specialized setting of the workshop allows for more extensive Q&A sessions and facilitates ample discussions,which may continue after the workshop. Typically, presentations of work-in-progress as well as of completed projects are welcome. The workshop may or may not produce formal proceedings.
- Retreats act as a platform for domain experts to gather with the purpose of tackling the issues of a predetermined research agenda. Retreats are highly interactive and goal-oriented, allowing their participants to address open challenges in their domain, to explore new, uncharted ideas, and to (maybe even) uncover new, promising research domains.
- Agenda-setting workshops provide a forum for domain experts to determine a research agenda for a sub-field, and may include collaborations on an agenda document that is published after the workshop is over.
Other common activities at workshops include poster sessions, hands-on practical work, and focus groups.
Proposal submitters should feel free to direct questions about workshop formats to the workshop chairs. Workshops that include presentation of research papers, and that implement a SIGPLAN-approved selection process, may be archived as formal proceedings in the ACM Digital Library; note that this option is available only to submitters to the early phase.
## Workshop Submission Phase:
This year, SPLASH provides two options to submit proposals, either Early Phase or Late Phase (but not both):
Early Phase Submissions due: 20 January 2017
Late Phase Submissions due: 3 March 2017
## Information
Website: http://2017.splashcon.org/track/splash-2017-Workshops <http://2017.splashcon.org/track/splash-2017-Workshops>
Email: workshops(a)splashcon.org <mailto:workshops@splashcon.org>
## Organization:
SPLASH General Chair: Gail Murphy (University of British Columbia)
OOPSLA Papers Chair: Jonathan Aldrich (Carnegie Mellon University)
Workshops Co-Chairs: Craig Anslow (Middlesex University, London) and
Alex Potanin (Victoria University of Wellington)
/************************************************************************************/
1
0
06 Jan '17
-----------------------------------------------------------------------
<Programming> 2017 : The Art, Science, and Engineering of Programming
April 3-6, 2017, Brussels, Belgium
http://2017.programming-conference.org
-----------------------------------------------------------------------
We are excited to announce there will be 10 co-located events at the
<Programming> 2017 conference (and more to come!):
- LASSY 2017 - 2nd Workshop on Live Adaptation of Software SYstems
- 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
- ELS 2017 - 10th European Lisp Symposium
- Modularity 2017 Invited talks - International Symposium on Modularity
- ACM Student Research Competition / <Programming> 2017 Posters
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)
******************************************************************
LASSY 2017 - 2nd Workshop on Live Adaptation of Software SYstems
Submissions: Fri 3 Feb 2017
Notifications: Fri 3 Mar 2017
http://2017.programming-conference.org/track/LASSY-2017-papers
******************************************************************
When developing current-day software systems, their deployment and usage
environments should be considered carefully, in order to understand the
adaptations those systems might need to undergo to interact with other
systems and with their environment. Moreover, due to the portability,
mobility and increasingly evolutionary nature of software systems, such
adaptations should be enacted even while the system is running.
Developing such software systems can prove challenging, and many
seemingly different techniques to address this concern have been
proposed over the last couple of years.
The intention of the LASSY workshop is to congregate all topics relevant
to dynamic adaptation and run-time evolution of software systems,
ranging from a computer science perspective covering the domains of
programming languages, model-driven software development, software and
service composition, context-aware databases, software variability,
requirements engineering, UI adaptation and other domains, to a human
perspective covering sociological or ethical implications of dynamic
software systems. The workshop provides a space for discussion and
collaboration between researchers working on the problem of enabling
live adaptations to software systems, across the development stack.
Topics of Interest:
* Design and Implementation of Live Adaptive Software Systems
* Context-, aspect-, feature-, role- and agent-oriented programming
* Context representation and discovery
* Context-aware model-driven software development
* Context-aware data management
* Software variability and dynamic product lines
* Self-adaptive, self-explanatory systems
* Inconsistency management, verification, and validation
* Middleware and Runtime of Live Adaptive Software Systems
* Dynamic software evolution, upgrades and configuration
* Dynamic software and service composition mechanisms
* Dynamic software architecture and middleware approaches
* Dynamic user interface adaptation and multimodal user interfaces
* Impact and Assessment of Live Adaptive Software Systems
* User acceptance and usability issues
* Human, sociological, ethical and legal aspects
* Privacy and security aspects of dynamic adaptability
* Live adaptation in smart environments (e.g. smart rooms,
smart robot cells, smart factories, smart cities)
* Self-adaptation and emergence in SoS and CPSoS
****************************************************************
MOMO 2017 - 2nd Workshop on Modularity in Modelling
Abstract submissions (optional): Sun Jan 29 2017
Paper submissions: Sun Feb 5 2017
Notifications: Wed Feb 22 2017
http://www.momo2017.ece.mcgill.ca/cfp.htm
****************************************************************
Extending the time-honored practice of separation of concerns,
Model-Driven Engineering (MDE) promotes the use of separate models to
address the various concerns in the development of complex
software-intensive systems. The main objective is to choose the right
level of abstraction to modularize a concern, specify its properties and
reason about the system under development depending on stakeholder and
development needs. While some of these models can be defined with a
single modelling language, a variety of heterogeneous models and
languages are typically used in the various phases of software
development. Furthermore, Domain-Specific Modelling Languages designed
to address particular concerns are also increasingly used.
Despite the power of abstraction of modelling, models of real-world
problems and systems quickly grow to such an extent that managing the
complexity by using proper modularization techniques becomes necessary.
As a result, many (standard) modelling notations have been extended with
aspect-oriented mechanisms and advanced composition operators to support
advanced separation of concerns, to combine (possibly heterogeneous)
models modularizing different concerns, to execute an application based
on modularized models, and to reason over global properties of
modularized models.
The Second International Modularity in Modelling Workshop brings
together researchers and practitioners interested in the theoretical and
practical challenges resulting from applying modularity, advanced
separation of concerns, and advanced composition at the modelling level.
It is intended to provide a forum for presenting new ideas and
discussing the impact of the use of modularization in the context of MDE
at different levels of abstraction.
We are interested in submissions on all topics related to modularity and
modelling including but not limited to:
* Modularization Support in Modelling Languages and Tools
* Model Interfaces
* Homogeneous Model Composition Operators
* Heterogeneous Model Composition Operators
* Visualization of Modularized and Composed Models
* Effects of Using Modularization and Composition in Modelling
* On Verification and Validation
* On Reuse
* On the Model-Driven Software Development Process
(Requirements Engineering, Software Architecture, Software Design,
Implementation)
* On Maintenance
* Experience Reports / Empirical Evaluations of Applying
Modularization and Composition in Modelling
* Feature-Oriented, Aspect-Oriented and Concern-Oriented Modelling
* Modularization support and composition operators for specific
modelling notations
* Modelling essential characteristics of specific
(crosscutting) concerns
* Multi-View Modelling: avoiding inconsistencies, avoiding
Redundancies
* Support for Detecting and/or Resolution of Feature Interactions
* Domain-Specific Modelling
* Modularization for Domain-Specific Languages
* Composition for Domain-Specific Languages
* Domain-specific Aspect Models
******************************************************************************
MoreVMs 2017 - 1st Workshop on Modern Language Runtimes, Ecosystems,
and VMs
Submissions: Wed 15 Feb 2017
Notifications: Wed 1 Mar 2017
http://2017.programming-conference.org/track/MoreVMs-2017-papers
******************************************************************************
The main goal of the workshop is to bring together both researchers and
practitioners and facilitate effective sharing of their respective
experiences and ideas on how languages and runtimes are utilized and
where they need to improve further. We welcome presentation proposals in
the form of extended abstracts discussing experiences, work-in-progress,
as well as future visions from the academic as well as industrial
perspective.
Relevant topics include, but are definitely not limited to, the following:
* Extensible VM design (compiler- or interpreter-based VMs)
* Reusable runtime components (e.g. interpreters, garbage
collectors, intermediate representations)
* Static and dynamic compiler techniques
* Techniques for compilation to high-level languages such as JavaScript
* Runtimes and mechanisms for interoperability between languages
* Tooling support (e.g. debugging, profiling, etc.)
* Programming language development environments and virtual machines
* Case studies of existing language implementations, virtual
machines, and runtime components (e.g. design choices, tradeoffs, etc.)
* Language implementation challenges and trade-offs (e.g.
performance, completeness, etc.)
* Surveys and applications usage reports to understand runtime
usage in the wild
* Surveys on frameworks and their impact on runtime usage
* New research ideas on how we want to build languages in the future
**************************************************************************
PASS 2017 - 1st Workshop on Programming Across the System Stack
Submissions: Mon 13 Feb 2017
Notifications: Mon 27 Feb 2017
http://2017.programming-conference.org/track/PASS-2017
**************************************************************************
The landscape of computation platforms has changed dramatically in
recent years. Emerging systems - such as wearable devices, smartphones,
unmanned aerial vehicles, Internet of things, cloud computing servers,
heterogeneous clusters, and data centers - pose a distinct set of
system-oriented challenges ranging from data throughput, energy
efficiency, security, real-time guarantees, to high performance. In the
meantime, code quality, such as modularity or extensibility, remains a
cornerstone in modern software engineering, bringing in crucial benefits
such as modular reasoning, program understanding, and collaborative
software development. Current methodologies and software development
technologies should be revised in order to produce software to meet
system-oriented goals, while preserving high internal code quality. The
role of the Software Engineer is essential, having to be aware of the
implications that each design, architecture and implementation decision
has on the application system ecosystem.
This workshop is driven by one fundamental question: How does internal
code quality interact with system-oriented goals? We welcome both
positive and negative responses to this question. An example of the
former would be modular reasoning systems specifically designed to
promote system-oriented goals, whereas an example of the latter would be
anti-patterns against system-oriented goals during software development.
Areas of interest include but are not limited to:
* Energy-aware software engineering (e.g. energy efficiency models,
energy efficiency as a quality attribute)
* Modularity support (e.g., programming language design,
development tools or verification) for applications in
resource-constrained or real-time systems
* Emerging platforms (e.g., Internet of Things and wearable devices)
* Security support (e.g., compositional information flow,
compositional program analysis)
* Software architecture for reusability and adaptability in systems
and their interactions with applications
* Empirical studies (patterns and anti-patterns) on the
relationship between internal code quality and system-oriented goals
* Software engineering techniques to balance the trade-off between
internal code quality and efficiency
* Memory bloats and long-tail performance problems across modular
boundaries
* Program optimization across modular boundaries
* Internal code quality in systems software
* Reasoning across applications, compilers, and virtual machines
****************************************************************
PX 2017 - 2nd Programming Experience Workshop
Submissions: Sat 4 Feb 2017
Notifications: Mon 27 Feb 2017
http://programming-experience.org/px17
****************************************************************
Imagine a software development task: some sort of requirements and
specification including performance goals and perhaps a platform and
programming language. A group of developers head into a vast workroom.
In that room they discover they need to explore the domain and the
nature of potential solutions—they need exploratory programming.
The Programming Experience Workshop is about what happens in that room
when one or a couple of programmers sit down in front of computers and
produce code, especially when it’s exploratory programming. Do they
create text that is transformed into running behavior (the old way), or
do they operate on behavior directly (“liveness”); are they exploring
the live domain to understand the true nature of the requirements; are
they like authors creating new worlds; does visualization matter; is the
experience immediate, immersive, vivid and continuous; do fluency,
literacy, and learning matter; do they build tools, meta-tools; are they
creating languages to express new concepts quickly and easily; and
curiously, is joy relevant to the experience?
Correctness, performance, standard tools, foundations, and
text-as-program are important traditional research areas, but the
experience of programming and how to improve and evolve it are the focus
of this workshop, and in this edition we would like to focus on
exploratory programming.
The technical topics include:
* Exploratory programming
* Live programming
* Authoring
* Representation of active content
* Visualization
* Navigation
* Modularity mechanisms
* Immediacy
* Literacy
* Fluency
* Learning
* Tool building
* Language engineering
*************************************************************************
ProWeb 2017 - 1st Workshop on Programming Technology for the Future Web
Submissions: Wed 15 Feb 2017
Notifications: Wed 1 Mar 2017
http://2017.programming-conference.org/track/proweb-2017-papers
*************************************************************************
Full-fledged web applications have become ubiquitous on desktop and
mobile devices alike. Whereas “responsive” web applications already
offered a more desktop-like experience, there is an increasing demand
for “rich” web applications (RIAs) that offer collaborative and even
off-line functionality —Google docs being the prototypical example. Long
gone are the days that web servers merely had to answer incoming HTTP
request with a block of static HTML. Today’s servers react to a
continuous stream of events coming from JavaScript applications that
have been pushed to clients. As a result, application logic and data is
increasingly distributed. Traditional dichotomies such as “client vs.
server” and “offline vs. online” are fading.
The 1st International Workshop on Programming Technology for the Future
Web, or ProWeb17, is a forum for researchers and practitioners to share
and discuss new technology for programming these and future evolutions
of the web. We welcome submissions introducing programming technology
(i.e., frameworks, libraries, programming languages, program analyses
and development tools) for implementing web applications and for
maintaining their quality over time, as well as experience reports about
the use of state-of-the-art programming technology.
Relevant topics include, but are not limited to:
* Quality on the new web: static and dynamic program analyses;
code, design test and process metrics; development and migration tools;
automated testing and test generation; contract systems, type systems,
and web service API conformance checking; …
* Hosting languages on the web: new runtimes; transpilation or
compilation to JavaScript, WebAssembly, asm.js, …
* Designing languages for the web: multi-tier (or tierless)
programming; reactive programming; frameworks for multi-tier or reactive
programming on the web; …
* Distributed data sharing, replication and consistency: cloud
types, CRDTs, eventual consistency, offline storage, peer-to-peer
communication, …
* Security on the web: client-side and server-side security
policies; policy enforcement; proxies and membranes; vulnerability
detection; dynamic patching, …
* Surveys and case studies using state-of-the-art web technology
(e.g., WebAssembly, WebSocket, LocalStorage, AppCache, ServiceWorkers,
Meteor, deepstream.io, Angular.js, React and React Native, Swarm.js,
Caja, TypeScript, Proxies, ClojureScript, Amber Smalltalk, Scala.js, …)
* Ideas on and experience reports about: how to reconcile the need
for quality with the need for agility on the web; how to master and
combine the myriad of tier-specific technologies required to develop a
web application, …
* Position statements on what the future of the web will look like
****************************************************************
Salon des Refusés 2017
Submissions: Wed 1 Feb 2017
Notifications: Fri 17 Feb 2017
https://refuses.github.io
****************************************************************
Salon des Refusés (“exhibition of rejects”) was an 1863 exhibition of
artworks rejected from the official Paris Salon. The jury of Paris Salon
required near-photographic realism and classified works according to a
strict genre hierarchy. Paintings by many, later famous, modernists such
as Édouard Manet were rejected and appeared in what became known as the
Salon des Refusés. This workshop aims to be the programming language
research equivalent of Salon des Refusés. We provide a venue for
exploring new ideas and new ways of doing computer science.
Many interesting ideas about programming might struggle to find space in
the modern programming language research community, often because they
are difficult to evaluate using established evaluation methods (be it
proofs, measurements or controlled user studies). As a result, new ideas
are often seen as “unscientific”.
This workshop provides a venue where such interesting and
thought-provoking ideas can be exposed to critical evaluation.
Submissions that provoke interesting discussion among the program
committee members will be published together with an attributed review
that presents an alternative position, develops additional context or
summarizes discussion from the workshop. This means of engaging with
papers not just enables explorations of novel programming ideas, but
also encourages new ways of doing computer science.
Topics of interest
The scope of the workshop is determined more by the format of
submissions than by the specific area of programming language or
computer science research that we are interested in. We welcome
submissions in a format that makes it possible to think about
programming in a new way, including, but not limited to:
* Thought experiments – we believe that thought experiments,
analogies and illustrative metaphors can provide novel insights and
inspire fruitful programming language ideas.
* Experimentation – we find prejudices in favour of theory, as far
back as there is institutionalized science, but programming can often be
seen more as experimentation than as theorizing. We welcome interesting
experiments even if there is yet no overarching theory that explains why
they happened.
* Paradigms – all scientific work is rooted in a scientific
paradigm that frame what questions can be asked. We encourage
submissions that reflect on existing paradigms or explore alternative
scientific paradigms.
* Metaphors, myths and analogies – any description of formal,
mathematical, quantitative or even poetical nature still represents just
an analogy. We believe that fruitful ideas can be learned from less
common forms of analogies as well as from the predominant, formal and
mathematical ones.
* From jokes to science fiction – a story or an artistic
performance may explore ideas and spark conversations that provide
crucial inspiration for development of new computer science thinking.
****************************************************************
ELS 2017 - 10th European Lisp Symposium
Submissions: Mon 30 Jan 2017
Notifications: Mon 27 Feb 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 / <Programming> 2017 Posters
Submissions: Mon 16 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. Please see our website for requirements and further details.
1
0