Home/ Questions/Q 748297
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T14:18:16+00:00

I’ve built an interpreter in C++ and everything works fine so far, but now

  • 0

I’ve built an interpreter in C++ and everything works fine so far, but now I’m getting stuck with the design of the import/include/however you want to call it function.

I thought about the following:

  • Handling includes in the tokenizing process: When there is an include found in the code, the tokenizing function is recursively called with the filename specified. The tokenized code of the included file is then added to the prior position of the include.
    Disadvantages: No conditional includes(!)

  • Handling includes during the interpreting process: I don’t know how. All I know is that PHP must do it this way as conditional includes are possible.

Now my questions:

  • What should I do about includes?
  • How do modern interpreters (Python/Ruby) handle this? Do they allow conditional includes?
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This problem is easy to solve if you have a clean design and you know what you’re doing. Otherwise it can be very hard. I have written at least 6 interpreters that all have this feature, and it’s fairly straightforward.

    1. Your interpreter needs to maintain an environment that knows about all the global variables, functions, types and so on that have been defined. You might feel more comfortable calling this the “symbol table”.

    2. You need to define an internal function that reads a file and updates the environment. Depending on your language design, you might or might not do some evaluation the moment you read things in. My interpreters are very dynamic and evaluate each definition as soon as it is read in.

    3. Your life will be infinitely easier if you structure your interpreter in layers:

      • Tokenizer (breaks input into tokens)
      • Parser (reads one token at a time, converts to abstract-syntax tree)
      • Evaluator (reads the abstract syntax and updates the environment)

    The abstract-syntax tree is really the key. If you have this, when you encounter the import/include construct in the input, you just make a recursive call and get more abstract syntax back. You can do this in the parser or the evaluator. If you want conditional import, you have to do it in the evaluator, since only the evaluator can compute a condition.

    Source code for my interpreters is on the web. Two of them are written in C; the others are written in Standard ML.

    • 0