here are many powerful programming models but most are not well supported by today's mainstream languages. concurrency is one. this talk will discuss the programming model of newsqueak, a concurrent programming language i designed and implemented to make it easier to write interactive applications in the late 1980s. it acts nothing like the tools used for that purpose today, but its ideas still have relevance. the language's users taught me a lot about concurrency, but they also taught me a lot

ll pugh present yet another installment in the continuing saga of java puzzlers, consisting of eight more programming puzzles for your entertainment and enlightenment. the game show format keeps you on your toes while the puzzles teach you about the subtleties of the java programming language and its core libraries. anyone with a working knowledge of the language will be able to understand the puzzles, but even the most seasoned veterans will be challenged. the lessons you take from this session

ed on a series of papers by philip wadler, a principal designer of the haskell programming language. featured are a number of double-barreled names in computer science: * hindley-milner (strong typing without having to type the types) * wadler-blott (making ad-hoc polymorphism less ad-hoc with parametricity) * curry-howard (isomorphism between types and theorems, terms and proofs) * girard-reynolds (isomorphism between types and terms in the presence of parametricity) the talk will conclude with

es, such as the concurrency apis and callbacks. more importantly, closures support control abstractions, which are apis that act as programmer-defined control constructs. this talk describes the proposed language extension and its design rationale, and shows how it will affect existing and future apis. credits: speaker:neal gafter

lti-thread performance than all other implementations i tried. i demonstrate scaling up to 768 cpus even with high mutation rates. i show correctness by looking at the problem in a very different light than the usual "happens-before" / memory-order / fencing style of thinking. speaker: dr. cliff click dr. cliff click, azul systems. chief jvm architect, distinguished engineer with more than twenty-five years experience developing compilers cliff serves as azul systems' chief jvm architect. cliff

current status of jsr-305, java annotations for software defect detection. this jsr will define several standard java annotations for properties such as @nonnegative and @nonnull that can be used to document your design intentions in a way that be interpreted by multiple software tools (such as findbugs and intellij). in addition, the talk (and jsr) will discuss the need for inherited and default jsr-305 annotations and propose a way to provide them. we'll also discuss our proposal to define met

mory model, which were incorporated into jdk 5, redefined the semantics of threads, synchronization, volatile variables, and final fields. the new memory model provides efficient and provably correct techniques for safely and correctly implementing concurrent operations. these techniques are compatible with existing good programming practice, although care needs to be taken in a couple of corner cases. most programmers can avoid depending on low-level details and instead just use the high-level

synchronization, and termination. this talk will present the current threading model and outline the remaining work. credits: speaker:lawrence crowl

r twenty years. this talk will be a discussion of major topics in overall gcc development, covering the efforts going on today, the plans for the future, and how google's gcc team is helping. credits: speaker:ian lance taylor

synchronization, and termination. this talk will present the current threading model and outline the remaining work.

es, such as the concurrency apis and callbacks. more importantly, closures support control abstractions, which are apis that act as programmer-defined control constructs. this talk describes the proposed language extension and its design rationale, and shows how it will affect existing and future apis.