You mean your company needs to COME FROM Intercal?
The 'computed COME FROM' is even more interesting than the regular one due to it's ability to violate causality by coming from a place in the code before it was ever computed.
That of course makes migrating from Intercal difficult for a lot of organizations.
PLEASE DO
PLEASE DO NOT ABSTAIN
I've had much success integrating Brainfuck in a legacy C++ codebase. As the team adopts modern idiomatic C++ patterns and practices, we found Brainfuck via https://github.com/tfc/cpp_template_meta_brainfuck_interpret... to be a natural and seamless fit for C++ template metaprogramming.
Buyer beware – as a a legacy mainframe user of INTERCAL (IBM VM/370), steer cleer of mainframe migration services that promise migration from INTERCAL to BF on commodity cloud on a fixed time scale – they use AI tools but don't do robust testing. Much better to stay on IBM but write new modules in enterprise z/INTERCAL, even if it's not the best developer environment.