PL EN


Preferencje help
Widoczny [Schowaj] Abstrakt
Liczba wyników
Powiadomienia systemowe
  • Sesja wygasła!
Tytuł artykułu

Low-Cost Dynamic Constraint Checking for the JVM

Autorzy
Treść / Zawartość
Identyfikatory
Warianty tytułu
Języki publikacji
EN
Abstrakty
EN
Using formal methods for software verification slowly becomes a standard in the industry. Overall it is a good idea to integrate as many checks as possible with the programming language. This is a major cause of the apparent success of strong typing in software, either performed on the compile time or dynamically, on runtime. Unfortunately, only some of the properties of software may be expressed in the type system of event the most sophisticated programming languages. Many of them must be performed dynamically. This paper presents a flexible library for the dynamically typed, functional programming language running in the JVM environment. This library offers its users a close to zero run-time overhead and strong mathematical background in category theory.
Rocznik
Strony
115--136
Opis fizyczny
Bibliogr. 22 poz.
Twórcy
autor
  • IT Institute, University of Social Sciences 9 Sienkiewicza St., 90-113 Lodz, Poland
Bibliografia
  • 1. Thomas M., 2016, How Can Software Be So Hard?, Gresham College Lecture, Feb. 2016, https://www.youtube.com/watch?v=VfRVz1iqgKU
  • 2. Thomas M., 2015, Should We Trust Computers, Gresham College Lecture, Oct. 2015, https://www.youtube.com/watch?v=8SZfjvlbpMw
  • 3. Pierce B.C., 2002, Types and Programming Languages, 1st Edition, MIT Press, ISBN-10: 0262162091, ISBN-13: 978-0262162098
  • 4. Pierce B.C., 2004, Advanced Topics in Types and Programming Languages, MIT Press, ISBN-10: 0262162288, ISBN-13: 978-0262162289
  • 5. Lamport L., 2002, Specifying Systems, The TLA+ Language and Tools for Hardware and Software Engineers, Addison Wesley, ISBN: 0-321-14306-X
  • 6. Lamport L., Paulson L.L., 1999, Should Your Specification Language Be Typed?, ACM Transactions on Programming Languages and Systems, Vol. 21, No. 3, pp. 502-526
  • 7. Emerick Ch., Carper B., Grand Ch., 2012, Clojure Programming, O’Reilly Media Inc., ISBN: 978-1-449-39470-7
  • 8. Fogus M., Houser Ch., 2014, The Joy of Clojure, Manning Publications; 2 edition, ISBN-10: 1617291412, ISBN-13: 978-1617291418
  • 9. Bird R., Wadler R., 1988, Introduction to Functional Programming. Series in Computer Science (Editor: C.A.R. Hoare), Prentice Hall International (UK) Ltd
  • 10. Awodey S., 2010, Category Theory, Second Edition, Oxford University Press
  • 11. Grzanek K., 2012, Prerequisites for Effective Requirements Management, Journal of Applied Computer Science Methods, Vol. 4, No 1, pp. 21-28
  • 12. Grzanek K., 2017, ch GitHub Repository, https://github.com/kongra/ch
  • 13. Grzanek K., 2017, ch Clojars Page, https://clojars.org/kongra/ch
  • 14. Grzanek K., 2017, prelude GitHub Repository, https://github.com/kongra/prelude
  • 15. Grzanek K., 2017, prelude Clojars Page, https://clojars.org/kongra/prelude
  • 16. Grzanek K., 2017, aptell GitHub Repository, https://github.com/kongra/aptell
  • 17. Clojure Team, 2017, clojure.spec Rationale, https://clojure.org/about/spec
  • 18. Clojure Team, 2017, clojure.spec Guide, https://clojure.org/guides/spec
  • 19. Plumatic, 2017, prismatic/schema GitHub Repository, https://github.com/ plumatic/schema
  • 20. Clojure Team, 2017, clojure/core.typed GitHub Repository, https://github.com/ clojure/core.typed
  • 21. CircleCI, 2015, Why we’re no longer using core.typed, https://circleci.com/blog/ why-were-no-longer-using-core-typed/
  • 22. Hacker News, 2015, Why were no longer using core.typed - discussion, https:// news.ycombinator.com/item?id=10271149
Typ dokumentu
Bibliografia
Identyfikator YADDA
bwmeta1.element.baztech-b07aeec9-77e9-47ae-b16f-5d2ba2c74184
JavaScript jest wyłączony w Twojej przeglądarce internetowej. Włącz go, a następnie odśwież stronę, aby móc w pełni z niej korzystać.