Hi,
Really interesting work.
I wonder if something similar could be done to bridge simdjson[1] with
Pharo/NeoJSON (and maybe a fast binary objects serializer) to read huge
JSON streams and files in seconds.
[1] https://github.com/lemire/simdjson
Thanks for this work :-),
Offray
On 1/01/20 4:4
Hello,
first of all, have a wonderful 2020..
sorry for jumping in, I'm not a contributor to Pharo, and actually never a
user of it ( when I work in Smalltalk, I use VW mostly, and still need to
find the time to try Pharo seriously), but I do work in Smalltalk (and
Pharo is a dialect of) from earl
On 2020-01-02 10:56 a.m., Sean P. DeNigris wrote:
While I dream of a world where everything is in-image as pure Smalltalk,
given the reality of limited manpower, I think of outside library use as a
way to "cheat" and get a lot more from that limited engineering resource.
Agree, I've used the or
On 2020-01-02 10:56 a.m., Sean P. DeNigris wrote:
While I dream of a world where everything is in-image as pure Smalltalk,
given the reality of limited manpower, I think of outside library use as a
way to "cheat" and get a lot more from that limited engineering resource.
Agree, I've used the or
Just while we are at the notion of markdowns, I have at
https://github.com/kasperosterbye/PillarRichTextRender a first build of a
pharo based github markdown to pillar. From pillar you can go to html.
But just to prove the point of the strength of importing working software
from outside using FFI,
Hi,
Good work :)
{ #category : #finalization }
HdBufferOpaque class >> finalizeResourceData: aHandle [
HdFFILibrary uniqueInstance
ffiCall: #(void hoedown_buffer_free (ExternalAddress aHandle))
]
wow… does this works at all?
I admit it is not how it is intended to work
--- Begin Message ---
+1
> On Jan 2, 2020, at 9:24 PM, Pierce Ng wrote:
>
> On Thu, Jan 02, 2020 at 12:56:55PM -0600, Sean P. DeNigris wrote:
>> bugs seem to be
>> more severe and difficult to diagnose, so we'll see how it goes as FFI use
>> becomes more and more common...
>
> There's a saying
On Thu, Jan 02, 2020 at 12:56:55PM -0600, Sean P. DeNigris wrote:
> bugs seem to be
> more severe and difficult to diagnose, so we'll see how it goes as FFI use
> becomes more and more common...
There's a saying about (aspects of) building software which source I
cannot recall:
If it hurts, do
On Thu, Jan 2, 2020 at 3:47 PM Sean P. DeNigris wrote:
>
> Tim Mackinnon wrote
> > I’m getting the impression that ffi is getting very easy these days and
> > maybe we should use it more to focus on “other” things... This said, many
> > of our nastiest bugs...
>
> That said, as you pointed out, bu
Tim Mackinnon wrote
> I’m getting the impression that ffi is getting very easy these days and
> maybe we should use it more to focus on “other” things... This said, many
> of our nastiest bugs...
While I dream of a world where everything is in-image as pure Smalltalk,
given the reality of limited
That makes sense - I’m getting the impression that ffi is getting very easy
these days and maybe we should use it more to focus on “other” things.
It does complicate deployment a bit - but if you’re server/cloud based then
that’s less of an issue anyway .
This said, many of our nastiest bugs s
Pierce Ng-3 wrote
> Also I saw hoedown's wiki page on bindings and thought I'd put Smalltalk
> on the map there.
Great!
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
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?
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
15 matches
Mail list logo
