Paper Details

db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
@InProceedings{Teig01a,
  title = "{F}rom {S}afe {C}oncurrent {P}rocesses to {P}rocess-{C}lasses? {PLUSSING} {N}ew {C}ode by {ROLLING} out and {C}ompile?",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
  author= "Teig, Øyvind",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
  editor= "Chalmers, Alan G. and Mirmehdi, Majid and Muller, Henk",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
  pages = "283--304",
  booktitle= "{C}ommunicating {P}rocess {A}rchitectures 2001",
  isbn= "1 58603 202 X",
  year= "2001",
  month= "sep",
  abstract= "This article expands a concurrent language to support
     implementation inheritance by making block structures of the
     super process-class pluggable, and to interface inheritance
     by making the language's protocol inheritable. The parallel
     'object-based' concurrent language occam 2 has been used as
     a catalyst for the concept, causing the language in fact to
     become (almost?) 'object-oriented' (OO). The result is
     white-box reuse between a 'process-class' and its sub
     process-class, and black-box reuse seen from the client
     side. Since occam is aliasing free and considered a 'safe'
     concurrent language, the expansion we discuss here keeps
     those properties - somewhat unusual for an OO system. This
     new language should be well suited in safety critical
     systems, since it has inherited the static (compile-time)
     and analysable properties from occam proper. Basically, two
     new keywords are defined: PLUSSING and ROLLING. The language
     feature suggestion is on sketch level only and therefore not
     complete, no BNF description exists and no compiler has been
     written."
}

If you have any comments on this database, including inaccuracies, requests to remove or add information, or suggestions for improvement, the WoTUG web team are happy to hear of them. We will do our best to resolve problems to everyone's satisfaction.

Copyright for the papers presented in this database normally resides with the authors; please contact them directly for more information. Addresses are normally presented in the full paper.