Jens Palsberg

Name: dblp XML data dump
Creator: Schloss Dagstuhl - Leibniz Center for Informatics
Published: 1993
License: https://creativecommons.org/publicdomain/zero/1.0/
Keywords: dblp, XML, computer science, scholarly publications, metadata

◀ ▶ joint publications with John Bender

> Home > Persons > Jens Palsberg

Publications

2022
[j71]
- view
  - electronic edition via DOI (open access)
  - references & citations
  authority control:
- export record
  dblp key:
  - journals/darts/LiuBP22
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/darts/LiuBP22
Shuyang Liu, John Bender, Jens Palsberg:
Compiling Volatile Correctly in Java (Artifact). Dagstuhl Artifacts Ser. 8(2): 03:1-03:2 (2022)
[c97]
- view
  - electronic edition via DOI (open access)
  - references & citations
  authority control:
- export record
  dblp key:
  - conf/ecoop/LiuBP22
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/ecoop/LiuBP22
Shuyang Liu, John Bender, Jens Palsberg:
Compiling Volatile Correctly in Java. ECOOP 2022: 6:1-6:26
2019
[j66]
- view
  - electronic edition via DOI (open access)
  - references & citations
  authority control:
- export record
  dblp key:
  - journals/pacmpl/BenderP19
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/pacmpl/BenderP19
John Bender, Jens Palsberg:
A formalization of Java's concurrent access modes. Proc. ACM Program. Lang. 3(OOPSLA): 142:1-142:28 (2019)
2015
[c83]
- view
  authority control:
- export record
  dblp key:
  - conf/oopsla/BenderLP15
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/oopsla/BenderLP15
John Bender, Mohsen Lesani, Jens Palsberg:
Declarative fence insertion. OOPSLA 2015: 367-385

a service of

manage site settings

To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.