Re: Prototype-Based Programming
- Posted by TheresNoTime Sep 28, 2013
- 2215 views
Manner dosn't matter - Erlang's messages, PowerShell's cmdlets, Zonnon's components... Euphoria's C-like DLLs are in a different row.
Agreed. That's because they do something entirely different and are meant for a different purpose. Don't compare apples to oranges.
So, I want cocktail. ;)
Take a look at what it takes to wrap a C library for Python http://docs.python.org/2/extending/extending.html or Java http://www.ibm.com/developerworks/java/tutorials/j-jni/
You did not want to understand the context in which the library is referenced. Python and Java not required C-DLLs in the sense in which I mentioned them. Python is possible to expand the standard means of Python. C-DLLs are used for speed or for access nonexistent features. But how to expand Euphoria? C-DLL?
I did not say I need it. It was an example of the Erlang's versatility.
This sounds plausible.
However, based on your serious and significant misunderstands of Euphoria, I'm reluctant to take your word for this. Instead, show me an example Erlang program which uses this capability and demonstrates Erlang's versatility.
It looks completely different. The closest analogy - two (or more) programs that operate in parallel and communicate via sockets.
There is no communication via socket in my example. I contend that my example is essentially the same as PowerShell's cmdlets - both execute a helper script (akak a cmdlet), passing arguments via the command line: http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-cmdlet/
Very funny. You found the manual, which says that the car can emit beeps and decided that the car - it's a hunting decoy.
Perhaps this complication in the form in which you are using it. Because there is no Euphoria means to do so, and your solution - it's a crutch. When the partition of the program into independent modules supported on the design level, it is a huge help.
Agreed. Although you can effectively write and use cmdlets-like scripts in Euphoria,
NO. You don't understand, what is cmdlets really. They are not programs, they are classes. Cmdlet is run not in a separate process, but inside PowerShell. This makes it possible to object exchange (in the sense of OOP) between cmdlets.
Concatenative programming languages do not have this problem because the scalability, in fact, the only element of the language. :)
All programming languages have their warts. E.g. http://www.erlang.org/faq/academic.html#id56798
http://mylazycoding.blogspot.com/2011/04/my-love-hate-relationship-with-erlang.html
and so on.
If I have to cross the terrain with sharp stones, I'd rather ditch the Ferrari, but do not go barefoot.
But how to glue DLLs writed in Euphoria? Get and send parameters by win32lib?
Either I do not understand documentation, or you do not understand what I meant. Please indicate appropriate chapter of manual by your finger.
I knew all this before. As I suspected, you do not understand me.
Clearly. You knew how to use dlls before, but thought you should have gotten and sent parameters by win32lib instead of the simpler dll interface?
Very well. Please explain how to glue DLLs writed (sic) in Euphoria via getting and sending parameters by win32lib.
OMG. Do not cling to the words. I do not remember such things, preferring every time specify in the documentation. Explain otherwise. It would be great if there was a standard way to establish communication between the two programs at Euphoria. For example, I pass the map to function and get a sequence. I can send to DLL a few numbers only. That's enough to send signals or memory addresses. You can make a loop and pass numbers one by one, then restore original format and order, but it is ugly. You can save to file, but it is fraught with collisions. And so on. There is no easy way. PowerShell have such way. Actually, this is how it works. When you send picture from one program to another by unix-pipeline, it seems like you put picture and get picture, but internally it is just bytes flow. When you send picture from one cmdlet to another cmdlet, it is picture internally.
