• Abstract and Figures
• Public Full-text

First-hand knowledge. Browse the Book In this chapter, you’ll learn about clean ABAP guidelines for a fundamen- tal building block in your ABAP code: methods. You’ll see how methods work with an object-oriented design and follow best practices for me- thod parameters, readability, and invocation. “Methods” Contents Index The Authors Klaus Haeuptle, Florian Hoffmann, Rodrigo Jordão, Michel Martin, Anagha Ravinarayan, Kai Westerholz Clean ABAP: A Style Guide for Developers 351 Pages, 2021, $79.95 ISBN 978-1-4932-2026-7 www.sap-press.com/5190 Chapter 4 Methods This chapter deals with clean ABAP methods. We’ll walk through key 4 method concepts such as method design, method body, and control flow. We’ll also explore the preferred way to call methods with clean ABAP. Methods are the ultimate containers of executable code in ABAP Objects. Other types of structures that directly contain code are function modules, programs, and subrou- tines, but as discussed in Chapter 2, Section 2.3, methods are the preferred low-level building blocks for clean ABAP code. Many other chapters in this book describe detailed clean code patterns and recommen- dations for ABAP code within methods. This chapter deals with the design, declaration, and usage of methods; high-level control flow within methods; method body guide- lines; and invoking methods. We’ll start with an in-depth discussion on methods in the context of object-oriented programming in Section 4.1. Then, in Section 4.2, we’ll dive deeply into method parameters and their use before turning, in Section 4.3, to clean code principles to apply to the method body. To finish this chapter, we’ll show you how to call your methods cleanly in Section 4.4. 4.1 Object-Oriented Programming In this section, we’ll discuss how to make methods work better within an object- oriented design, picking up on our earlier discussion of object-oriented programming in Chapter 3, Section 3.1. 4.1.1 Static and Instance Methods Static methods are methods declared with the CLASS-METHODS keyword and are attached to the class itself, not to instances of the class. To call a static method, you’ll use the class name directly, without needing to create an instance of that class. In this way, static methods are not truly object-oriented. They do not participate in the class inher- itance hierarchy and do not participate in dynamic dispatch (thus, the term “static”). Listing 4.1 shows you how to declare a static method. 95 4Methods 4.1 Object-Oriented Programming CLASS blog_post DEFINITION Also, the behavior of instance methods can be redefined and more easily mocked in PUBLIC. unit tests. Their data scope is the scope of the class instance, and resources can be con- figured per instance. For these reasons, we recommend using instance methods by PUBLIC SECTION. default, rather than static methods. 4 CLASS-METHODS: Look at the related discussion involving classes in Chapter 3, Section 3.1.2. publish. Methods should be static in the following cases: for static creation methods and for ENDCLASS. utility methods. Listing 4.1 Static Method Definition Static creation methods are methods that work as specialized constructors (as described earlier in Chapter 3, Section 3.3.3). These methods return an instance of the owning You can call this method using the class name directly, followed by a fat arrow (=>): class or a subclass, as shown in Listing 4.3, where the create_as_copy method serves as a static creation method by creating a copy of the passed in source_blog_post instance. blog_post=>publish( ). CLASS blog_post DEFINITION Since static methods constrain the behavior to a specific implementation, they are not PUBLIC. flexible. Instance methods, meanwhile, are attached to instances of the class. Instance methods PUBLIC SECTION. are declared with the METHODS keyword, as shown in Listing 4.2. CLASS-METHODS: CLASS blog_post DEFINITION create_as_copy PUBLIC. IMPORTING source_blog_post TYPE REF TO blog_post PUBLIC SECTION. RETURNING VALUE(result) TYPE REF TO blog_post. METHODS: publish. ... ENDCLASS. ENDCLASS. Listing 4.2 Instance Method Definition Listing 4.3 Static Creation Method Example To call an instance method, you need an instance of the class, followed by a thin arrow Utility methods are methods that don’t depend on any underlying resources and per- (->): form a static operation that is not reasonably expected to change and does not need DATA my_blog_post TYPE REF TO blog_post. any parameterized behavior. These methods should usually be part of a utility class ... that provides related operations (see Chapter 3, Section 3.1.2). An example of the defini- my_blog_post->publish( ). tion of a utility method is shown in Listing 4.4, where the fahrenheit_to_celsius method performs a simple temperature conversion. This kind of operation does not require any variation and is perfectly fine as a utility method. Consider Using Instance Methods by Default CLASS temperature_conversion DEFINITION The key to the flexibility of instance methods is the fact that they are attached to PUBLIC instances of classes. At runtime, a specific instance could refer to any subclass in the ABSTRACT hierarchy of the declared class variable (including itself), which makes the method call FINAL. “dynamic” or “virtual.” 96 97 4Methods 4.1 Object-Oriented Programming PUBLIC SECTION. Public Instance Methods Should Be Part of an Interface CLASS-METHODS fahrenheit_to_celsius For a class to serve as a good citizen in an overall design, the class should implement IMPORTING interfaces that define its abstract behavior. Consequently, most, if not all, of its public temperature_in_fahrenheit TYPE temperature instance methods should be part of an interface. 4 RETURNING In this way, the class itself becomes a mere implementation of the concepts repre- VALUE(result) TYPE temperature. sented by the interfaces it implements, and consumers don’t need to depend directly on the class at all. This important step enables the dependency inversion principle, the ... D in SOLID. ENDCLASS. Not all classes need to implement interfaces. Exception classes, value objects (see Chap- Listing 4.4 Utility Method Example ter 3, Section 3.1.2), and enumeration classes (see Chapter 6, Section 6.2.2), for example, usually don’t need to present an abstraction over their operations and, as such, aren’t Both static and instance methods are implemented with the METHOD … ENDMETHOD con- usually backed by interfaces. In general, classes that represent values or entities that struct in the class implementation area, as shown in Listing 4.5 for the static method only contain data, and not services, won’t implement interfaces. temperature_conversion=>fahrenheit_to_celsius. For more information about interfaces and their advantages, refer to Chapter 3, Section CLASS temperature_conversion IMPLEMENTATION. 3.1.1. Let’s revisit and improve the design of the thermal_switch class presented in Chapter 3, METHOD fahrenheit_to_celsius. Section 3.1.2, specifically in Listing 3.15. The thermal_switch class’s main service is to pro- result = ( temperature_in_fahrenheit - 32)*5/9. ENDMETHOD. tect a wrapped device from overheating. Its methods are trip (to trip the switch and turn the device off) and reset (to reset the switch to a normal state), which were imple- ENDCLASS. mented as direct public instance methods on the class. To make those methods into interface methods and better abstract consumers of a Listing 4.5 Static Method Implementation thermal protector from the specific implementation present in the thermal switch, we can extract the interface thermal_protector, as shown in Listing 4.6. Don’t Call Static Methods through Instance Variables INTERFACE thermal_protector It is possible to call a static method through an instance of a class. However, a static PUBLIC. method is attached to the class itself, and calling it through an instance is redundant and a potential source of confusion. METHODS: Make the fact that you’re calling a static method clear by always qualifying the method trip call with the class name. FOR EVENT critical_temperature_reached OF thermal_sensor, reset. 4.1.2 Public Instance Methods ENDINTERFACE. Public instance methods in a class effectively define its interface to outside consumers. Listing 4.6 The thermal_protector Interface Anyone with access to the class can call that class’s public instance methods. The thermal_switch class now implements thermal_protector, which results in all its To better manage dependencies and improve isolation, you should decouple from con- public instance methods being backed by interfaces. Listing 4.7 shows its refactored crete classes and focus on the abstraction that the class presents. In this way, replacing PUBLIC SECTION. implementation details with alternative implementations, like mock instances for testing, will be easier. 98 99 4Methods 4.1 Object-Oriented Programming CLASS thermal_switch DEFINITION Let’s revisit the fan class we introduced in Chapter 3. Now, let’s say we have a new FINAL requirement to create a fan subclass that steps over multiple values when its intensity PUBLIC. is changed. We can redefine the appropriate methods with the desired implementa- tion, as shown in Listing 4.8. PUBLIC SECTION. CLASS step_fan DEFINITION 4 INTERFACES: PUBLIC switchable, FINAL thermal_protector. INHERITING FROM fan. ALIASES: PUBLIC SECTION. trip FOR thermal_protector~trip, reset FOR thermal_protector~reset. METHODS: constructor METHODS: IMPORTING step TYPE int4, constructor increase_intensity REDEFINITION, IMPORTING decrease_intensity REDEFINITION.

Load more

  34

Copy Link