On Tuesday 30 June 2009 22:35:44 J. R. Mauro wrote:
On Jun 30, 2009, at 22:24, Mike Frysinger wrote:
On Tuesday 30 June 2009 21:47:18 J. R. Mauro wrote:
please dont top post
Who did?
i'm guessing you made this comment ironically
On Jun 30, 2009, at 21:42, Alex Camilo <alex.camilo@gmail.com> wrote:
I'm trying to extend the functionality of a piece of CAD software i'm using. The software package is called eagle and it has a custom in application scripting language that allows you to access an open CAD document by manipulating a tree of objects. The scripting language is fairly limited when it comes to talking to the outside world and only offers rudimentary file IO. I was wondering if any of you know how to make one end of a unix socket look like a file?
Unfortunately, you can't. It's one of the design flaws of Unix. You might be able to wrap it with a FUSE filesystem. But sockets and FIFOs are unfortunately "special"
i imagine you could use netcat to redirect from a named pipe so that you can
FIFOs are kind of a hack.
no one said otherwise. the fun thing about *nix is you can leverage these kind of hacks quickly.
Make a fuse filesystem in 20 lines of python and you get something more robust and specialized, plus network transparency for free
if you say so, i havent done fuse work myself -mike