{"id":6843,"date":"2024-08-08T11:48:23","date_gmt":"2024-08-08T09:48:23","guid":{"rendered":"https:\/\/oopm.org\/?page_id=6843"},"modified":"2025-01-17T09:26:39","modified_gmt":"2025-01-17T08:26:39","slug":"49-notation","status":"publish","type":"page","link":"https:\/\/oopm.org\/?page_id=6843","title":{"rendered":"24. Notation"},"content":{"rendered":"
\"image_pdf\"<\/a>\"image_print\"<\/a><\/div>\n

This chapter explains the notation used in this book.<\/p>\n\n\n\n

Program text<\/h2>\n\n\n\n

The program examples shown in this book are made in the qBeta language. The elements of the language are introduced as they are needed to illustrate the programming elements presented in the book. For a comprehensive description of qBeta see the web-site qbeta.dev<\/a>.<\/p>\n\n\n\n

Abbreviations<\/h2>\n\n\n\n

For practical purposes, we do not always show all the code in the examples and we use the following notation for code not shown:<\/p>\n\n\n\n

    \n
  • The symbols -\"-<\/code> stands for code, which has been shown in a previous example. You may think of the -\"-<\/code> as an extended ditto-sign.<\/li>\n\n\n\n
  • The symbols :::<\/code> stands for code, which will be shown later \u2013 often in the same section.<\/li>\n\n\n\n
  • The symbols ...<\/code> stands for code, which is not shown and left to the reader to fill in.<\/li>\n<\/ul>\n\n\n\n

    Diagrams and illustrations<\/h2>\n\n\n\n

    In this section, we summarise the diagrams<\/em> used to show different kinds of elements of programs and program executions. Diagrams are partial since they only show selected elements of a given program or program execution, but they are formal\/exact\/precise in the sense that they show elements that are present in the program or program execution.<\/p>\n\n\n\n

    \n
    \n

    We also use illustrations<\/em> in the form of informal drawings or pictures to illustrate a given text in the book, a given application domain, etc.<\/p>\n\n\n\n

    An example is this photo used in section