With the mechanics for handling eval in place, no special tricks are needed to specialize call/cc. It is only necessary to provide a binding-time specification which ensures that no memoization point appears between abstraction and use of the continuation so that the discarded part of the continuation of the specializer coincides with the continuation of the evaluator. In addition, the specializer should not transmit code fragments containing free dynamic variables through the captured continuation. Our binding-time type system ensures both: for (call/cc (lambda (c) ...)) to be static the lambda expression must be completely static and not memoized. The same must hold for the continuation variable c. It does not matter in what context (static or dynamic) call/cc occurs: A call/cc can be executed statically in a dynamic context unless the continuation escapes.