On Wed, Jan 01, 2020 at 02:35:03PM +0100, Tim Mackinnon wrote:
> I’m curious why you chose to use ffi for this one in particular as it
> would seem to be quite straightforward to do it all in native
> Smalltalk (not to down play your integration in any way of course).
> Was performance a big thing?
https://medium.com/@richardeng/how-can-we-celebrate-the-50th-anniversary-of-smalltalk-e6b35dbc09a9
--- Begin Message ---
Hello,
I have it now working but as you said there is a lot of code smells and
my exact question is how to get rid of them.
solution
| computer |
computer := self new.
computer readRam: computer masses.
computer patchRam: 1 value: 12.
computer pat
I’m loving all the little utility libraries coming out (and appreciate the
write ups on how things are done).
I’m curious why you chose to use ffi for this one in particular as it would
seem to be quite straightforward to do it all in native Smalltalk (not to down
play your integration in any w
Hi all,
I've published Phoedown, an FFI to hoedown, the standards compliant, fast,
secure Markdown
processing library written in C.
- https://github.com/PierceNg/Phoedown
- https://github.com/hoedown/hoedown
A simple example:
| md |
md := (FileSystem memory / 'somefile.md')
wr