[Lldb-commits] [lldb] [LLDB] Add AST node classes, functions, etc. for Data Inspection Lang… (PR #95738)

[via lldb-commits]

================
@@ -0,0 +1,459 @@
+//===-- DILAST.h ------------------------------------------------*- C++ -*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+//
+//===----------------------------------------------------------------------===//
+
+#ifndef LLDB_CORE_DILAST_H
+#define LLDB_CORE_DILAST_H
+
+#include <memory>
+#include <optional>
+#include <string>
+#include <variant>
+#include <vector>
+
+#include "lldb/Core/ValueObject.h"
+#include "lldb/Symbol/Type.h"
+#include "lldb/Symbol/TypeList.h"
+#include "lldb/Target/LanguageRuntime.h"
+#include "lldb/Utility/ConstString.h"
+#include "clang/Basic/SourceLocation.h"
+#include "clang/Basic/TokenKinds.h"
----------------
cmtice wrote:

ok, then we've run into a very serious problem:  the DIL implementation (and lldb-eval, on which it was based) makes extensive use of Clang for parsing & lexing.  I'm *guessing* the best way to handle this is to try to bundle the parsing/lexing stuff into some kind of plugin, with different plugins for the different languages?  OR...is it possible that the small language subset that DIL wants to parse/lex/evaluate is roughly the same across all the languages?

I'm really not sure about the best way forward here...

https://github.com/llvm/llvm-project/pull/95738