1. overview
1.1 'what is' about Dylan
1.1.1 what is Dylan? A imperative, functional and OOP language
Short definition of imperative, functional and OOP languages with Dylan examples
Functional view
The usefulness of functional programming
should Dylan show up in this list of functional languages?
learning the Functional Programming paradigma first?
Please define lambda expression
OOP view
Dylan's Generic Function system
1.1.2 what is Dylan's different world view?
1.1.3 What is out standing about Dylan?
1.1.4 what is Dylan? A language list description.
1.1.5 What is Dylan? Carefully designed
1.1.6 What is Dylan future?
Hopes
Worries
1.2 'what is not' about Dylan
1.2.1 Dylan is not Lisp
1.2.2 Dylan is not designed for "Hello world" apps
1.3 How to help newcomers to the language get the right "mental models?
1.3.1 What is the core feature of Dylan? Object-oriented function calls, not objects
paradigma shift side notes
1.3.2 Dylan language design principles
provide abstraction facilities as well as performance
readability before writability
flexibility versus deliverability
syntax
Designed for large blocks of code with really-long-variable-names
Designed with infix syntax to reach the mainstream
Break basic things up into libraries
IDE
1.3.3 Is Dylan complex?
1.3.4 What metal leaps are required
from variables-in-c to variables-in-dylan; from pointer reference to object reference
Am I a backwards thinker, with my brain stuck in C mode?
How to do the mental gear shift single-dispatch OOP to multi method dispatch?
1.3.5 What are the key aspects during the design of Dylan?
1.3.6 What is your background?
For Scheme Programmers
For LISP Programmer
1.4 things I like most about Dylan
1.4.1 the balance
1.4.2 no reason for programmers to know how any particular implementation
1.4.3 ability to pass methods, functions, and classes around as first class objects
1.4.4 OS Versions
libraries are packaged as DLL's
2. Programm Control
2.1 multi-value binds
2.1.1 How are local multi-value-bind's done in Common Lisp and Dylan?
2.1.2 How are multi-value-bind's done?
2.1.3 How are multi-values return by a method?
2.1.4 how to capture an unknown number of multiple return values into a sequence?
3. concept
3.1 binding
3.1.1 to do
3.1.2 Binding and Scoping
Is not allowed to use one name for different bindings
scoping constructs
In Dylan you can't create bindings at runtime
3.1.3 module binding
what's the inverse of 'define variable ' and 'define method' ?
3.1.4 local binding
every time you see the word 'let' a NEW lexical context created
why is 'let' allowed to float around?
Dylan's interpretation of let
3.1.5 assignment
cannot assign a new value to an existing binding (variable) with let
reassigning a new value to the variable doesn't affect the old value in any way.
let creates and initializes new local bindings within the scope of the smallest enclosing implicit body.
3.1.6 variables
Think of variables as labels
3.1.7 syntax
Talking about let using "=" while assignment uses ":="
The syntax for global and local definitions
3.2 libraries and modules
3.2.1 design
Why always contains the first line in the library definition file "Module: dylan-user"?
Why aren't the "define module" declarations nested within the "define library" ones? So you can easily have two libraries which include the same module.
Would a type signature of methods at the module level be an improvement?
why modules don't nest.
3.2.2 goals
abstraction
How is the separation of interface and implementation done? Via a set of "define generic" and "define abstract class" forms and .
Separating abstraction level via rename at the module level
namespace mangement
What are the scopes of namespaces
How does a coder prevent scoping clashes?
How does a client handle scoping clashes?
What are the impacts of the module system? Puts the namespace naming into the consumer's hand
No access to the namespace required
3.2.3 usage
Good use of module
What are the roles of modules and the definition clauses that modules use?
export
Why should I put \ in front of macro and operator exports?
Modules are the unit of interface, libraries are the unit of *compilation*
3.3 Contracting
3.3.1 generic function represent "contracts" or "interfaces"
3.4 types and classes
3.4.1 types
some types are not classes in Dylan
general
Does Dylan have a type protocoll?
Why no null?
instantiable types
What types are instantiable?
Who can create new instantiable types?
limited types
What supports the limited operation for creating new types?
Collection subtyping issue due to limited types
strongly typed, but not statically typed
in Dylan the types are all first-order: you can't declare higher-order types
3.4.2 classes and slots
Exploring the difference between the Dylan model and other OO models.
Classes are not namespaces
Objects no longer encapsulate the message
How are instance variables accessed
Features of Classes
abstract or concrete
Why using open abstract and sealed concrete in one class hierarchy?
Abstract and instantiable Class are separate concepts in Dylan
primary or free
How to use the primary declaration effectively?
sealed or open
What's a sealed class
Why would a type be sealed but not primary?
instantiable or uninstantiable
Creating Classes
Can you mutate an object from one class to another?
creating classes at runtime
What is the language mechanism for specifying the default concrete class for an abstract class?
Initialize Classes
Introspecting Classes
about slots
general
Can one add slots to a class a runtime?
How to generate object methods with the same name? or Remember that slots in Dylan are really just generic functions
dot syntax
How works a slot reference?
what you should know
Slot allocation
How to implement the each-subclass slot allocation?
Is there away to access "class allocated" slots without having an instance of that class?
How to control slot-accessor collisions? By adequately specific names and by use of the module system.
Is there a way to access "class allocated" slots without having an instance
Slot initialization
How defaulting #"default" to a value?
Slot init value
Slot inheritance
Retyping inherited slots?
Specializing Slots
virtual slots
What the practical use for a virtual slot
3.4.3 singleton
How is singleton dispatch implemented efficiently?
singleton returnable by make?
3.5 Functions
3.5.1 general
Generic Functions
What does generic mean ?
What's a generic function?
Where can I read up more of generic function implementation?
what generic function gets defined by default as I define methods
A generic function can act on different (required) objects, but still using different number of optional parameters
pragmatic
return type constraints of sub-domains of generic functions
Methods
Closure
Discussing the DRM closure example
other examples
making two function: fetcher and incrementer
using closures and map
value of closures
Closures form the backbone the exception-handling system and the macro expansion system.
In languages without closures ...
MultiDispatch
Which papers inform about it?
Intro
The Basic: single-receiver languages and multi-method languages.
The dispatching mechanism
for C++ people
Why multimethods and how they would work in C++
Multimethods as a C++ extension
for Java people
Why Multiple Polymorphism is better
Why Dynamic Inheritance is better
multimethods removes much of the need for parameterized types
The mechanism
Dylan's dispatching system is type based.
Dylan's dispatch system is inheritance based: next-method
The method precedence rules are non-lexicographic
Pragmatic -- -how to use
The rules of thumb for multimethods and modules
Have you to define (+ <int> <real>) and (+ <real> <int>) separately?
Parameter Lists
Specializing Required Parameters
Convient syntax for singleton specializers
Keyword Parameters
What are keyword parameters?
Specialised keyword parameters
naming convention
! operations
immutable syntax vs. ! convention
Thinking
artificial examples that help to break the idea that methods are tied to classes
3.5.2 built-in-function
coercion function "as"
higher-order functions
apply
Why it is defined the way it is
curry
reduce
map
3.6 Collection
3.6.1 general
Discussing the remove contract
Creating a New Collection
3.6.2 pragmatic
Prefer collection iteration to indexing
How to use ! operations. Example: reverse!
Annotations to collection specification required
Hashing: Hash code and Hash states
3.6.3 iteration
when to use a iteration protocoll
3.6.4 limited collection types
modify an existing API to use limited collections instead of "regular" collections, you'll break clients.
3.6.5 built-in collection classes
table
general
How to write your own <table> implementation
changing comparator for <table>?
table protocol
Changed the table-protocol?
What are hash states?
Any examples of custom hash functions
sequence
list
What does the term "dotted list" mean?
How to find a specific item in a collection
array
vector
limited <stretchy-vector>
How to subclass vector
Using "#[]" versus "vector()"
a clean way to a vector
Why are sets excluded from Dylan Built-In Classes?
3.7 dynamic
3.7.1 in what way is Dylan dynamic
3.7.2 dynamic loading
How to use the ability to dynamically load code from a DLL at run time
Binary modularity of dylan Libs
3.7.3 dynamic code generating
3.7.4 dynamic persistency
3.7.5 dynamic typing
3.7.6 dynamic languages
dynamic language
3.8 exceptions
3.8.1 intro
view on the mechanism
The practical side of things
step-by-step explanation
3.8.2 general
Exception chapter of DP
Exception by Design: ANSI Exception handling
handling multiple exceptions
Comparing Dylan's Condition Handling to the one of LISP
3.8.3 restart
Restarts in Dylan
the neat part: you can retrofit <restart>s onto an existing API
3.8.4 types
violating the contract of a function
violating the type constraint on a slot or variable
accessing an uninitialized slot
3.9 sealed domains
3.9.1 overview
What's the goal?
What's the rationale for method sealing via the "seal?
Why can a sealed class can have open subclasses? The specific proposal gives an answer.
The nice things about sealing declarations
3.9.2 Define Seal Domain
Implied Restrictions on Method Definitions
sealed domain
3.9.3 pragmatic
Can you import classes/generic functions from another library and then seal them?
Is "sealed" a local property of a given class rather or a global property of the entire class hierarchy?
3.10 macros
3.10.1 Why macros
What you can expect form the macro system
syntactic burden of lambdas
The ultimate abstraction
3.10.2 mechanism
Dylan macros are hygenic
What are hygenic macros
How to do a non-hygenic reference
Why couldn't a parser expand a macro as soon as it saw the ending token?
Wildcard patterns
pattern variable coercion
Dylan macros maintain referential transparency
3.10.3 pragmatic
Every implementor has to break a lot of new ground every time
3.10.4 designing macros
What a competent macro designer must know
How to design macros
Guidelines for writing good macros
3.10.5 rule format
The function format: function macro
example
increment!
swaping the content of two places
Returning the least of its arguments.
The statement format: statement macro
example
with-open-file
with-stack-list to indicate that a list has dynamic extent
with-stack-vector to indicate that a vector has dynamic extent
fluid-binding that isn't thread-safe
destructuring-let simulates CL's 'destructuring-bind'
The definition format: defining macro
example
functional-variable
named-color
Hairy one that defines a class with slots and some methods
3.10.6 usage
Resource management via with-xxx macros
see discussion
Who is an expert
3.10.7 todo
Semantic of "?="
tutorial
facilities of the macro syste,
see archive 2000
DP Chapter 21
3.11 metaobject protocoll (MOP)
3.12 Multi Inheritance (MI)
3.12.1 What MI is in C++ and What MI is in Dylan (CLOS or whatever)
3.12.2 benefit example
code for an user interface toolkit
3.13 Performance
3.13.1 What feature support optimization?
3.13.2 Is there any Dylan implementation with a GC good enough for *soft* real-time use
3.13.3 for benchmarking use concrete types
3.13.4 What kind of effect does generic dispatch have on performance?
3.14 introspection
3.14.1 What when i want to know what methods my class supports?
3.15 iteration
3.15.1 via for macro
3.16 syntax
3.16.1 opinions
Why the Dylan syntax is different to C/C++ and Algol
syntax opinions: an impression
3.16.2 What is often misunderstood about the use of 'begin'
3.16.3 examples
if
3.16.4 Better Dylan Syntax
3.16.5 Changing the syntax is possible
3.17 style of object model
3.18 unit and mixin
3.18.1 mixin layers
3.18.2 Traits: mixin inheritance
3.18.3 Mixins using multiple inheritance
3.19 parallel
About
Title
DylanTalks
Subject
-
Company
-
Author
-
Version
196
Comments
-