On Thu, Oct 19, 2017 at 1:05 AM, Todd Blanchard <tblanch...@mac.com> wrote:

> I'm working through Ben's great blog post about playing with libclang and
> I am puzzled by something.
>

Thx Todd. Knowing someone is looking at it encourages me to expand it.
I'm interested in looking at your specific questions, but it might not be
until next week after this stint of long work days.

cheers -ben



>
> invalidateSessionData
>    handle atAllPut: 0.
>
> zero;s out the handle.  Cool.  However,
>
> handle isNull
>
> does not return true despite it being used in the getString method as
>
> ^ handle isNull
>          ifTrue: ['external memory invalidated by session restart']
>          ifFalse:[LibClang clang_getCString__cxString: self].
>
> Looks like there should be an isNull on ByteArray that returns true if all
> bytes are zero but it isn't  there.  Was it dropped for some reason?
>
>
>
> On Oct 18, 2017, at 2:58 AM, Dimitris Chloupis <kilon.al...@gmail.com>
> wrote:
>
> Sure the documentation could be better, that is definetly important, but
> is already good enough and UFFI is a very technical subject much more
> suited to a mailing list . Its not physical possible to cover the massive
> potential of UFFI.
>
> On Wed, Oct 18, 2017 at 9:32 AM Stephane Ducasse <stepharo.s...@gmail.com>
> wrote:
>
>> Please do not hesitate to do Pull Requests.
>> Luc told me that he wants to do a pass on it and Esteban promises that to
>> me
>> but he is super busy.
>>
>> Stef
>>
>>
>> On Wed, Oct 18, 2017 at 5:54 AM, Todd Blanchard <tblanch...@mac.com>
>> wrote:
>> > Wonderful!  Thanks.
>> >
>> >> On Oct 17, 2017, at 3:45 PM, stephan <step...@stack.nl> wrote:
>> >>
>> >> On 17-10-17 23:06, Todd Blanchard wrote:
>> >>> Anyone know what happened to this?
>> >>> https://ci.inria.fr/pharo-contribution/view/Books/job/
>> PharoBookWorkInProgress/lastSuccessfulBuild/artifact/
>> book-result/UnifiedFFI/UnifiedFFI.pdf
>> >>
>> >> https://github.com/SquareBracketAssociates/Booklet-uFFI
>> >>
>> >> has a link to a bintray pdf download
>> >>
>> >> Stephan
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>

Reply via email to