Book Image

Getting Started with V Programming

By : Navule Pavan Kumar Rao
4 (1)
Book Image

Getting Started with V Programming

4 (1)
By: Navule Pavan Kumar Rao

Overview of this book

A new language on the block, V comes with a promising set of features such as fast compilation and interoperability with other programming languages. This is the first book on the V programming language, packed with concise information and a walkthrough of all the features you need to know to get started with the language. The book begins by covering the fundamentals to help you learn about the basic features of V and the suite of built-in libraries available within the V ecosystem. You'll become familiar with primitive data types, declaring variables, arrays, and maps. In addition to basic programming, you'll develop a solid understanding of the building blocks of programming, including functions, structs, and modules in the V programming language. As you advance through the chapters, you'll learn how to implement concurrency in V Programming, and finally learn how to write test cases for functions. This book takes you through an end-to-end project that will guide you to build fast and maintainable RESTful microservices by leveraging the power of V and its built-in libraries. By the end of this V programming book, you'll be well-versed with the V programming language and be able to start writing your own programs and applications.
Table of Contents (19 chapters)
1
Section 1: Introduction to the V Programming Language
4
Section 2: Basics of V Programming
12
Section 3: Advanced Concepts in V Programming

Working with modules

The modular programming approach offers maintainability and code re-usability. It also helps you to add abstractions and allows you to expose only necessary functionality to the consumers of the module. It is recommended that you learn how to work with modules and examine how to efficiently create and organize applications whose functionality span across modules. In this section, you will learn about the various principles to define and work with modules:

  • The directory name must match the module name.
  • Imported modules must be consumed in the code.
  • Multiple V files in the module must define the same module.
  • Both private and public members of a module can be accessed from anywhere within the module.
  • Only public members of the module are accessible outside of the module.
  • Cyclic imports are not allowed.
  • Define init functions to execute one-time module-level initializer functionality.

All of the V code that is shown later in this...