| |||||||||||||
Embedding vs. extendingEmbedding vs. extendingPosted Dec 5, 2012 0:16 UTC (Wed) by civodul (subscriber, #58311)In reply to: GNU Guile 2.0.7 released by dakas Parent article: GNU Guile 2.0.7 released Note that it is often more fruitful to extend Guile (or Python, or ...), than to embed it. See this section of Guile's manual, and this article about Python for some discussion.
(Log in to post comments)
Embedding vs. extending Posted Dec 6, 2012 20:48 UTC (Thu) by dvdeug (subscriber, #10998) [Link]
The discussions don't seem to target my issues at all. When I'm thinking of embedding a language, it's because I have a program that I would like for people to be able to extend; say a graphics program that people want an easy way to write plugins for, or a game that people want to write AIs for. I may well want for certain environments to be able to not compile in a 3MB Python interpreter. The Python one asks "do you want your application to inter-operate with other applications that Python can use?" Why would I? I'm not building a library here; why is it vitally important that Gimp and Quake can run at the same time?
Embedding vs. extending Posted Dec 6, 2012 21:19 UTC (Thu) by andrel (subscriber, #5166) [Link]
Well if your goal is to automate a pipeline which starts with a Quake screenshot and process it in GIMP to get the final output, then yes you want them both running at the same time.
Embedding vs. extending Posted Dec 6, 2012 23:16 UTC (Thu) by dvdeug (subscriber, #10998) [Link]
Why? You produce the screenshot, and send it through the pipeline and send it into GIMP. No need to bring everything into one process.
|
|||||||||||||