I write software that is far less complex and I consider it to be "thinking" while it is working through multiple possible permutations of output and selecting the best one. Unless you rigidly define thinking, processing, computing, it's reasonable to use them interchangeably.
To borrow a line from Dijkstra, the claim seems a bit like saying that a submarine is swimming.