newlispfanclub.alh.net

Here is an example of how a simple echo server might look: (load "libevent2.lsp") (setf listen (net-listen 8000)) (unless listen (throw-error (net-error))) (libevent:init) (libevent:watch listen libevent:READ (lambda (fd e id , client) ; accept a new connection (setf client (net-accept listen)) ; wa...

Actually, that is not exactly true. That is more how signals work, although not in libevent. In libevent, the application is controlled by the loop. Before starting the loop, you register at least one socket or timer to run in it. It is an error to run a loop with no events registered. For example, ...

Howdy folks. Haven't been around in a while. Wanted to let you know that I put together a wrapper for libevent2 using the new FFI features. Made it very easy. You can find it on github here - https://github.com/jsober/nl-event.

Without checking the code again, it looks like you are doing things right. Unfortunately, I do not have a lot of time for personal projects at the moment. If you can find the bug and fix it, I would be happy to update the sources on my site and google projects.

Le pido perdon. Hablo solamente ingles y espanol. Y lisp ;)

Was he trying to append "-Schwanz" or "-Schwanz-Schwanz-Schwanz"?

In fact, I think *I* may have written that :)

You need to pass map a function. You can do that with curry:

Thank you, Lutz. This is exactly the hook we need to extend the language. This is a good thing for the language. Will reader-event be hooked into run-time compilation as well? That is, when I call read-expr, will the expression be first run through reader-event? I believe it should, so that translat...

Lutz, one other thing. Shouldn't this be reader-event, not read-event?
Neither is documented in the manual.

That's not what I meant. I meant that it would be nice to have the type of compile-time expansion you built using read-expr but in the context of a non-defining expression. More like letex than define, in other words. That way we could use them as part of a regular newlisp macro. Like the backtick i...

You know, Lutz, it would be nice if there were an operator that expanded at compile-time, rather than the entire function definition. That way, it could be evaluated inside a macro and provide the full power of both f-expressions and compile-time syntax transformations.

newlisp's new send/receive functions to communicate between processes are very nice. They let you write coroutines between processes.

Also check out the news forum. I just wrote a module wrapping eventlib, which adds event-based processing for sockets.

This nice thing about these macros is that you are actually performing a compile-time transformation on the code. You can use them to easily define destructive setters on OOP classes, for example, because they would translate into the actual code that returns a reference. Perhaps something like this...

Hey folks, I am in the process of polishing up the interface to a wrapper module around libevent, an asynchronous I/O library for Windows, Linux, Unix, and OSX. What is asynchronous I/O? Threading and multiprocessing are expensive ways to take advantage of multi-core systems. They add complexity to ...

Thanks. That will make my life easier every time the wordpress geshi plugin gets an update :)

And I am no giant. I am under 6 foot. I don't even know what, "fee fie foe fum," means!

dostring processes a string one char at a time...

If the preferred method to avoid variable capture is to use lexically scoped macros, why not make all macros lexically scoped by default? Why not have the reader implicitly read local variables in a macro as if the macro were written: (context 'my-macro) (define-macro (my-macro ...) ...) (context 'p...

Thanks!

Does net-receive block while waiting on wait-string if:

1) it is not found before int-max-bytes are read
2) it is not found in the bytes immediately available from the remote socket

If it does block for situation 2, is there any way to evade that behavior while still using the built-in buffer?

I think an extension api with the following components would let us do whatever is necessary: 1) an include with the major types - nil, cell, symbol, etc 2) a shared library would have an "init" function that calls a macro or function that registers a function with newlisp; it would also have a "clo...

Or use 'eval'.

It would be nice to have a more robust API to extend newlisp from C, though. The "extend rather than embed" philosophy of Python is equally applicable to newlisp. I write a lot of C libraries and end up spending a lot of time gluing the code together with newlisp. A few glue functions in a shared li...

Remember that function arguments are passed by value - that is, they are copied on every call. You can avoid this by assigning a large value to a symbol and passing the symbol itself to the function instead.

Here is a tutorial on drilling down into xml content in newlisp:

http://www.artfulcode.net/articles/working-xml-newlisp/

Here is a tutorial on using find-all with xml (among others) in newlisp:

http://www.artfulcode.net/articles/usin ... -find-all/