Thread: Google and c

Originally Posted by MK27

I just mention this because it kind of sounds like someone has taken a very wacky, excessively complex route to accomplish a fairly straightforward task, and if you are interested in learning about things like this, you are being led astray...

Hence my Rube Goldberg machine comment

Originally Posted by Angel45

The reason there is so many lines of code is because the information is being stored into text files everywhere.

If you're using what I suggested, then you should just be storing the data in memory. If you do write to file, it will because you are writing the translation obtained from the service to file as output.

Originally Posted by Angel45

And everything is getting evaluated twice to get the correct size for malloc to be called.

What do you mean by "evaluated twice"?

Originally Posted by Angel45

It gets exactly what the chrome developers tools get, which is .html, with .js as I believe. We technically are not even running that code, we are just collecting and reorganizing it to display just the results which are stored in the code.

Then that sounds like you are not actually leveraging the developer tools. My impression is that you used the source inspection from the developer tools, decided that you would like to parse that for the translated text, and so went about trying to leverage the developer tools do that.

But the truth is that if you just want to get the translated text, then trying to format source in the same way as the developer tools is pointless. You might need the source of the page in order to get certain pieces of data so as to mimic the AJAX request to the service, but you don't need to mimic what the developer tools do. You need to mimic what the script on the page itself does.