IRC channel logs
2025-04-12.log
back to list of logs
<rlb>I somewhat strongly suspect that scm_t_option handling is corrupting memory here now. <rlb>(presumably via gc issue, i.e. no mark function) <rlb>In the current case, the SCM_PRINT_HIGHLIGHT_PREFIX_I assignment in scm_init_print, causes other, subsequent members of the scm_print_opts array to change. <rlb>or maybe it's some other cause, but it definitely causes the change. <rlb>I think this may not be the first time I've been side tracked by an accidental (char=? ch) returning #f instead of crashing... <ArneBab>old: wisp modules are just scheme modules. The semantics are exactly the same. To import them from scheme, you just need to have them auto-compiled first (the *.go files are fully compatible). You may have to add -x .w as commandline argument, so the .w files are recognized and the .go files used instead. <ArneBab>old: keep in mind, though, that wisp always has SRFI-105 active (#!curly-infix). <old>ArneBab: I've had experienced with GWL in the past and I like that you can provide a frontend for the user in Wisp and the backend is in Scheme <old>as long as the two worlds does not collide too much <dadinn>The conversation was stuck back then, but I stumbled on it today, so I thought I'll have a look if I can still rebase the code on the current main branch. <dadinn>It is essentially a rewrite of the (ice-9 expect) module using hygienic macro, instead of the original defmacro implementation. <dadinn>It should be completely backwards compatible, so there should be no need for any migration of old codez. <dadinn>Yet it supports quite powerful new forms, and is quite robust... much more so than the defmacro implementation, which can get corrupted in certain expansions. <dadinn>Anyway, if the community would be still interested, get in touch on the email thread above, on the guile-devel mailing list.