Re: [Chicken-users] Live programming with Chicken

2014-07-03 Thread Kristian Lein-Mathisen
That is strange, I've experienced alex's problem too - having to yield a
little to give the REPL some room.

Anyhow, for others who might come across this thread: alex's idea works
great, but you need to be careful with blocking IO on your REPL. If you
don't use parley http://api.call-cc.org/doc/parley or something similar,
chances are that your REPL srfi-18-thread will block your
srfi-18-game-thread while it's waiting for IO.

K.


On Wed, Jul 2, 2014 at 9:07 PM, John Cowan co...@mercury.ccil.org wrote:

 alex scripsit:

  I had some trouble with this last part at first: the original thread
  waited several seconds before evaluating my input. I think that the
  fix was nothing more than calling thread-yield! every loop
  iteration.

 If you are depending on thread-yield! for correctness rather than
 efficiency, you are doing something wrong (but I don't know what).
 SRFI 18 schedulers are not required to be fair in any way.

 --
 John Cowan  http://www.ccil.org/~cowanco...@ccil.org
 He that would foil me must use such weapons as I do, for I have not
 fed my readers with straw, neither will I be confuted with stubble.
 --Thomas Vaughan (1650)

 ___
 Chicken-users mailing list
 Chicken-users@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/chicken-users

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Live programming with Chicken

2014-07-03 Thread Daniel Leslie
Unless I missed a radical change in Chicken, its SRFI-18 threads are green
threads and not real system threads. As a result, blocking operations will
block all threads and no real gain is had from the hardware's support for
multithreading.

Because of those issues I suggest avoiding SRFI-18 threads altogether. They
aren't worth the hassle.

-Dan
On 3 Jul 2014 04:13, Kristian Lein-Mathisen kristianl...@gmail.com
wrote:

 That is strange, I've experienced alex's problem too - having to yield a
 little to give the REPL some room.

 Anyhow, for others who might come across this thread: alex's idea works
 great, but you need to be careful with blocking IO on your REPL. If you
 don't use parley http://api.call-cc.org/doc/parley or something
 similar, chances are that your REPL srfi-18-thread will block your
 srfi-18-game-thread while it's waiting for IO.

 K.


 On Wed, Jul 2, 2014 at 9:07 PM, John Cowan co...@mercury.ccil.org wrote:

 alex scripsit:

  I had some trouble with this last part at first: the original thread
  waited several seconds before evaluating my input. I think that the
  fix was nothing more than calling thread-yield! every loop
  iteration.

 If you are depending on thread-yield! for correctness rather than
 efficiency, you are doing something wrong (but I don't know what).
 SRFI 18 schedulers are not required to be fair in any way.

 --
 John Cowan  http://www.ccil.org/~cowanco...@ccil.org
 He that would foil me must use such weapons as I do, for I have not
 fed my readers with straw, neither will I be confuted with stubble.
 --Thomas Vaughan (1650)

 ___
 Chicken-users mailing list
 Chicken-users@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/chicken-users



 ___
 Chicken-users mailing list
 Chicken-users@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/chicken-users


___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


[Chicken-users] Dbus egg crashes in Chicken 4.9

2014-07-03 Thread Oleg Kolosov
Hello.

After upgrading to Chicken 4.9 our application started to crash in dbus
egg. The culprit was found in changed semantics of the assoc and
friends: it now checks that the supplied argument is a list. The
attached patch fixes the problem. I've not checked if there are similar
problems somewhere else.

-- 
Regards, Oleg
diff -ru dbus.orig/dbus.scm dbus/dbus.scm
--- dbus.orig/dbus.scm	2014-06-19 15:02:24.0 +0400
+++ dbus/dbus.scm	2014-06-19 15:10:17.998005481 +0400
@@ -272,7 +272,7 @@
 	(define (tassq tree . keys)
 		(let ([key-list (if (pair? (car keys)) (car keys) keys)])
 			(let loop ([rem-keys key-list][subtree tree])
-(if (null? rem-keys)
+(if (or (not subtree) (null? rem-keys))
 	subtree
 	(loop (cdr rem-keys)
 		(let ([pr (assq (car rem-keys) subtree)])
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Dbus egg crashes in Chicken 4.9

2014-07-03 Thread Shawn Rutledge
I found that a couple of days ago; try again with the svn trunk.  I
will have to make a new release soon.

It's interesting that you are getting some use out of it; does it work
well enough and make sense?  What kind of application?

On 3 July 2014 20:35, Oleg Kolosov bazur...@gmail.com wrote:
 Hello.

 After upgrading to Chicken 4.9 our application started to crash in dbus
 egg. The culprit was found in changed semantics of the assoc and
 friends: it now checks that the supplied argument is a list. The
 attached patch fixes the problem. I've not checked if there are similar
 problems somewhere else.

 --
 Regards, Oleg

 ___
 Chicken-users mailing list
 Chicken-users@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/chicken-users


___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Fwd: Re: Active Windows users poll

2014-07-03 Thread Oleg Kolosov
On 06/17/14 17:48, Pedro Melendez wrote:
 I would vote for that too. Some eggs might be a little tricky to port
 though. I remember having troubles with a networking egg on cygwin.
 
 Can't wait to see this :)
 
 
 On Tue, Jun 17, 2014 at 2:39 AM, Yaroslav Tsarko
 eriktsa...@googlemail.com mailto:eriktsa...@googlemail.com wrote:
 
 
 
 
  Original Message 
 Subject:  Re: [Chicken-users] Active Windows users poll
 Date: Mon, 16 Jun 2014 14:52:40 +0200
 From: Richard plui...@freeshell.de mailto:plui...@freeshell.de
 To:   Yaroslav Tsarko eriktsa...@googlemail.com
 mailto:eriktsa...@googlemail.com
 
 
 
 Hello Oleg,
 
 I too would greatly welcome a Window build. Thank you
 
 On 06/16/14 13:24, Yaroslav Tsarko wrote:
  Hi Oleg!
 
  Those are great news!
 
  I am very interested in this project since native Windows build is 
  preferable when you work on Windows
  rather than mingw tricks. This will greatly shorten Chicken dependency 
  list for Windows - one don`t need to install mingw stuff to build 
  Chicken with eggs on Windows and use platform tools instead.
 
  On 15.06.2014 01:21, Oleg Kolosov wrote:
  Hello All!
 
  I'm working on new build system for Chicken, based on CMake which,
  besides more configurability and faster build times, can offer native
  Windows and MacOSX support with Visual Studio, XCode and other IDEs
  integration. I also can make installer with few eggs bundled and such.
 
  The system already allows seamless integration with CMake projects and
  tested on Linux. But doing full Windows port is more involved 
  unfortunately.
 
  So, if anybody interested in native Windows port of Chicken, give 
  your vote.

Thanks to all who replied! This certainly encourages the development.

Whether it will be accepted by the Chicken developers is still a big
question, there are still a lot of issues which needs resolving. But I
will continue to work on this anyway for solving our company internal needs.

I occasionally put the changes on github:
https://github.com/bazurbat/chicken-scheme and
https://github.com/bazurbat/cmake-modules. The support for integrating
Chicken with existing CMake projects is quite solid already. If you are
interested in early access or testing feel free to contact me directly.

-- 
Regards, Oleg

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users