Herencia e interfaces
Utilice la herencia para reutilizar código y defina API de contratos claras mediante interfaces para mejorar la modularidad.
Herencia e interfaces es una lección gratuita de Blockchain Smart Contracts with Solidity en CoddyKit. Esta es la lección 1 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Blockchain Smart Contracts with Solidity, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Blockchain Smart Contracts with Solidity incluye 4 lecciones en total.
Partes de esta lección aún no han sido traducidas y se muestran en inglés.
What is Inheritance?
In Solidity, inheritance allows one smart contract (the child) to reuse code, functions, and state variables from another contract (the parent). This is a fundamental concept in object-oriented programming.
- It promotes code reusability.
- It helps organize complex contract logic.
- It allows for modular and extensible designs.
Basic Inheritance Syntax
To make a contract inherit from another, you use the is keyword. The child contract gets access to all public and internal members of the parent contract.
Think of it like a child inheriting traits from its parent.
pragma solidity ^0.8.0;
contract ParentContract {
uint public parentValue;
constructor() {
parentValue = 100;
}
function getParentValue() public view returns (uint) {
return parentValue;
}
}
contract ChildContract is ParentContract {
// ChildContract inherits parentValue and getParentValue()
}Inheriting Functions & State
When ChildContract inherits from ParentContract, it automatically gains access to parentValue and the getParentValue() function. You can directly interact with them from the child contract.
Let's deploy ChildContract and see its parent's value!
pragma solidity ^0.8.0;
contract ParentContract {
uint public parentValue;
constructor() {
parentValue = 100;
}
function getParentValue() public view returns (uint) {
return parentValue;
}
}
contract ChildContract is ParentContract {
function getMyParentValue() public view returns (uint) {
return getParentValue(); // Calling an inherited function
}
function getDirectParentValue() public view returns (uint) {
return parentValue; // Accessing an inherited state variable
}
}Overriding Functions
Sometimes, a child contract needs to provide its own implementation for a function that already exists in the parent. This is called overriding.
To override a function:
- The parent function must be marked with
virtual. - The child function must be marked with
override. - Function signatures (name, parameters, return types) must match exactly.
Override Example
Here, the ChildContract provides a new behavior for greet(). Notice the virtual and override keywords.
pragma solidity ^0.8.0;
contract GreeterParent {
function greet() public virtual view returns (string memory) {
return "Hello from Parent!";
}
}
contract GreeterChild is GreeterParent {
function greet() public override view returns (string memory) {
return "Hello from Child!";
}
}Calling Parent Functions with 'super'
When you override a function, you don't always have to completely replace its logic. You can still call the parent's version of the function within the overriding function using super.
This is useful for extending or modifying parent behavior instead of replacing it entirely.
pragma solidity ^0.8.0;
contract Base {
function foo() public virtual pure returns (string memory) {
return "Base foo";
}
}
contract Derived is Base {
function foo() public override pure returns (string memory) {
string memory baseMessage = super.foo(); // Call parent's foo()
return string(abi.encodePacked(baseMessage, " and Derived logic"));
}
}What are Interfaces?
A Solidity Interface is like a blueprint or a contract without any implementation. It defines the public functions that a contract must have if it claims to implement that interface.
- They specify what functions exist and their parameters/return types.
- They do not contain any function bodies or state variables.
- All functions in an interface are implicitly
external.
Interface Syntax & Purpose
Interfaces are declared using the interface keyword. They are crucial for:
- Standardization: Ensuring contracts adhere to specific public APIs (e.g., ERC-20 token standard).
- Interoperability: Allowing contracts to interact with other contracts without knowing their full implementation details, only their interface.
- Modularity: Decoupling contract designs.
pragma solidity ^0.8.0;
interface ICalculator {
function add(uint a, uint b) external pure returns (uint);
function subtract(uint a, uint b) external pure returns (uint);
}Implementing an Interface
A contract can implement an interface using the is keyword, similar to inheritance. When a contract implements an interface, it must provide concrete implementations for all functions declared in that interface.
pragma solidity ^0.8.0;
interface IGreeter {
function greet() external view returns (string memory);
function setGreeting(string calldata _greeting) external;
}
contract MyGreeter is IGreeter {
string private currentGreeting = "Hello, World!";
function greet() public view override returns (string memory) {
return currentGreeting;
}
function setGreeting(string calldata _greeting) public override {
currentGreeting = _greeting;
}
}Quick Check: Inheritance vs. Interface
Which of the following statements about Solidity inheritance and interfaces is TRUE?
Recap: Inheritance & Interfaces
We've explored two powerful concepts in Solidity for building modular and reusable smart contracts:
- Inheritance: Allows a child contract to reuse code and logic from a parent using the
iskeyword. Functions can bevirtualin the parent andoverridein the child, andsupercan call parent logic. - Interfaces: Define a contract's public API without implementing its logic. They use the
interfacekeyword and ensure contracts adhere to specific function signatures, promoting standardization and interoperability.
Mastering these patterns is key to writing robust and maintainable Solidity code!
Aprende Blockchain Smart Contracts with Solidity con un tutor de IA — gratis
Escribe y ejecuta código real en tu navegador, obtén ayuda instantánea de un tutor de IA disponible 24/7 y continúa donde lo dejaste en la web o en la aplicación.
- Cursos
- 12
- Lecciones
- 48
Preguntas frecuentes
¿La lección «Herencia e interfaces» es gratis?
Sí — el texto completo de «Herencia e interfaces» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Blockchain Smart Contracts with Solidity, actualiza a CoddyKit PRO. El curso de Blockchain Smart Contracts with Solidity incluye 4 lecciones en total.
¿Qué aprenderé en «Herencia e interfaces»?
Utilice la herencia para reutilizar código y defina API de contratos claras mediante interfaces para mejorar la modularidad. Practicas Blockchain Smart Contracts with Solidity con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.
¿Necesito experiencia previa para empezar Blockchain Smart Contracts with Solidity?
No se requiere experiencia previa. Blockchain Smart Contracts with Solidity en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 1 de 4.
¿Cuánto tiempo toma la lección «Herencia e interfaces»?
La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.
¿Puedo escribir y ejecutar código en esta lección de Blockchain Smart Contracts with Solidity?
Sí. Cada lección de Blockchain Smart Contracts with Solidity incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.
Todas las lecciones de este curso
- Herencia e interfaces
- Librerías y contratos abstractos
- Gestión de errores con Revert/Require
- Modificadores y el patrón checks-effects-interactions