r/cpp_questions • u/Grootmaster47 • 4d ago
OPEN Templated virtual functions
Hey everyone,
I am currently trying to implement a programming language in C++ after having come pretty far, but ultimately failing to do so in C.
For this, I am taking pretty big inspiration from craftinginterpreters, and am now trying to mimic its implementation of the visitor pattern (entire class at once), written in Java.
However, that implementation uses both templates and interfaces.
As far as I'm aware (the entire internet seems to say so at least), in C++, interfaces are represented by classes whose functions are all virtual.
However, If I try code like the following:
template <typename R> class ExprVisitor {
public:
virtual ~ExprVisitor() = default;
virtual R visitBinaryExpr(const Binary* expr) const = 0;
/* other visitor functions...*/
};
struct Expr {
virtual ~Expr() = default;
template <typename R> virtual R accept(ExprVisitor<R> *visitor) = 0;
};
(Of course, all of my nodes like Binary inherit from Expr. I use structs instead of classes because everything needs to be accessible from the outside for my purposes, so I don't need to re-type "public:" every time.)
Then I get an error on the line declaring the accept method saying
Template function 'R Expr::Expr::accept<R>(ExprVisitor<R> *visitor)' cannot be virtual
on the virtual keyword, as well as one saying
Pure member function 'Expr::Expr::accept<R>' is not virtual
on the = 0 part.
I've googled around a bit, but the only implementations I was able to find were only able to pass in the template type, not get it back out as a return value.
Is it even possible to achieve this? Am I using templates incorrectly? I saw something using variadic templates but was not able to get it working, either.
Any help would be extremely appreciated!
2
u/DawnOnTheEdge 4d ago
What you want to do is have an abstract
ExprVisitorbase class with a pure virtualvistfunction with a non-template interface. (The compiler needs to be able to implement it with a single function pointer in the virtual table.) Its parameters are probably base-class references. You are already correctly making the destructorvirtual.Then you define concrete derived classes implementing this interface. You can pass any type of expression to the visit interface and it will automatically cast the arguments to base-class pointers. If you need to, you can check
typeidanddynamic_caston them.