@amirouche where is the blocking happening? if it is on a file descriptor then Gambit's green threads will be sufficient because the thread scheduler multiplexes the CPU so that Scheme threads waiting on a fd are put to sleep without blocking other threads. Scheme-level mutexes and condition variables also don't block other threads than the one blocking.
the main resource used is cpu
My first implementation was as Marc said to spawn an OS thread (a pthread in my case) and have the thread communicate “completion” by sending 1 byte down a named pipe. The named pipe is only read on the Gambit side where the Gambit thread will be blocked and only written on the C side. Later on, when porting to Windows where named pipes are a bit different and touchy to use, I tried replacing the named pipes by TCP sockets and tests showed performance to be identical as the OS clearly optimizes the special case of same machine (in this case even same process) communication. All this works very well for my needs and with it I can now play 80 movies at the same time on my mac (160 Gambit threads blocked on receiving codec data).
Hi Marc, I've noticed a few bugs in Not Emacs on iOS. Among others, there's no way to close the initial Help Window, you can't quit Scheme (pressing Ctrl-D several times doesn't work), and "yank from operating system" displays a window into which you can't paste text from other iOS applications. Furthermore, being able to open files from iCloud or DropBox would be a bonus. If I were a C/iOS programmer, I could probably fix those bugs myself, but I'm not. Can you help? Many thanks. Cheers, P
Hi, has anyone ever tried "spawn" on iOS? If so, was it stable?
@jazzscheme Yes there's a zlib implementation in pure Scheme in the bigloo source code. I used that to make a zlib snow ball many years ago. And now I've revived the code for the next release of Gambit. I also have a tar module.
Warning: require_once(/Users/gambit/Sites/wiki/skins/.php) [function.require-once]: failed to open stream: No such file or directory in /Users/gambit/Sites/wiki/includes/Skin.php on line 144
The Gambit at 30 meeting will be October 12-13. Please register ASAP and tell your friends! https://mailman.iro.umontreal.ca/pipermail/gambit-list/2019-September/009152.html
assuming slack handing out non-valid unicode values again?
Gambit and Scheme newb here, although I've been programming in Clojure for several years now. While reading "Tour of Scheme in Gambit" I tried to pust "(module hello)" in a .scm file, and load it with gsi. It gives me an unbound variable error noting "module". How does one use "module" and "use"?
@pwhittin Gambitscheme.org is not reachable for me ATM, but from memory i think "Tour of Scheme in Gambit" talked about the "Blackhole" module system. It was never part of gambit (bundled within the gambit repo) and i think it can be considered phased out / deprecated. AFIK your current options for a module-system with gambit (besides using "load" and "include" and thus managing everything, especially dependencies, by hand) is use either the gerbil dialect or the newly but not fully documented built-in module system which is documented in the info-page. I you can wait a little bit, i think the r7rs module system will be released for gambit soon. No promises here, it's just that Marc indicated something like this.
*** ERROR -- Unbound variable: sc#datum->syntax
loading it with
(##include "~~/lib/syntax-case.scm")
Hello All, this semester I am taking a class on programming languages and we are using gambit. we use gambit through our schools server via putty. I understand enough of emacs in order to work on my code. However, I wanted to edit my code in my preferred text editor and then just run the code through cmd. So I installed gambit and it installed properly but whenever I try to run my code using gsi [insert file name].scm a window flashes for a second and then disappears. Is there anyway that I can get the window to stay open or is there a way I can just get the code to run in terminal like when I run a c++ program?
Another way is:
gsi program.scm -e "(read)"
Are you using gsi from the Windows command prompt window or from a MSYS shell window?