A critical analysis of string APIs: The ...
Type de document :
Compte-rendu et recension critique d'ouvrage
Titre :
A critical analysis of string APIs: The case of Pharo
Auteur(s) :
Pollet, Damien [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Ducasse, Stephane [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Ducasse, Stephane [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Titre de la revue :
Science of Computer Programming
Pagination :
1-12
Éditeur :
Elsevier
Date de publication :
2017-11
ISSN :
0167-6423
Mot(s)-clé(s) en anglais :
Style
Strings
API
Design
Library
Strings
API
Design
Library
Discipline(s) HAL :
Informatique [cs]/Langage de programmation [cs.PL]
Informatique [cs]/Génie logiciel [cs.SE]
Informatique [cs]/Génie logiciel [cs.SE]
Résumé en anglais : [en]
Most programming languages, besides C, provide a native abstraction for character strings, but string APIs vary widely in size, expressiveness, and subjective convenience across languages. In Pharo, while at first glance ...
Lire la suite >Most programming languages, besides C, provide a native abstraction for character strings, but string APIs vary widely in size, expressiveness, and subjective convenience across languages. In Pharo, while at first glance the API of the String class seems rich, it often feels cumbersome in practice; to improve its usability, we faced the challenge of assessing its design. However, we found hardly any guideline about design forces and how they structure the design space, and no comprehensive analysis of the expected string operations and their different variations. In this article, we first analyse the Pharo 4 String library, then contrast it with its Haskell, Java, Python, Ruby, and Rust counterparts. We harvest criteria to describe a string API, and reflect on features and design tensions. This analysis should help language designers in understanding the design space of strings, and will serve as a basis for a future redesign of the string library in Pharo.Lire moins >
Lire la suite >Most programming languages, besides C, provide a native abstraction for character strings, but string APIs vary widely in size, expressiveness, and subjective convenience across languages. In Pharo, while at first glance the API of the String class seems rich, it often feels cumbersome in practice; to improve its usability, we faced the challenge of assessing its design. However, we found hardly any guideline about design forces and how they structure the design space, and no comprehensive analysis of the expected string operations and their different variations. In this article, we first analyse the Pharo 4 String library, then contrast it with its Haskell, Java, Python, Ruby, and Rust counterparts. We harvest criteria to describe a string API, and reflect on features and design tensions. This analysis should help language designers in understanding the design space of strings, and will serve as a basis for a future redesign of the string library in Pharo.Lire moins >
Langue :
Anglais
Vulgarisation :
Non
Collections :
Source :
Fichiers
- https://hal.inria.fr/hal-01651250/document
- Accès libre
- Accéder au document
- http://arxiv.org/pdf/1711.10713
- Accès libre
- Accéder au document
- https://hal.inria.fr/hal-01651250/document
- Accès libre
- Accéder au document
- https://hal.inria.fr/hal-01651250/document
- Accès libre
- Accéder au document
- document
- Accès libre
- Accéder au document
- mainJournal.pdf
- Accès libre
- Accéder au document
- 1711.10713
- Accès libre
- Accéder au document