Park SungMin writes:
> (let ((c-type (list int int (make-list 2 int
> (parse-c-struct
> ((pointer->procedure
>c-type
>(dynamic-func "make_foo" libfoo)
>(list int int))
> 4 11)
> c-type))
>
> also run well…but seems less effective.(if more bigger
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Mar 30, 2016 at 10:03:28AM +0200, Taylan Ulrich Bayırlı/Kammer wrote:
> Park SungMin writes:
>
> > (let ((c-type (list int int (make-list 2 int
> > (parse-c-struct
> > ((pointer->procedure
> >c-type
> >(dynami
writes:
> On Wed, Mar 30, 2016 at 10:03:28AM +0200, Taylan Ulrich Bayırlı/Kammer wrote:
>> Park SungMin writes:
>>
>> > (let ((c-type (list int int (make-list 2 int
>> > (parse-c-struct
>> > ((pointer->procedure
>> >c-type
>> >(dynamic-func "make_foo" libfoo)
>>
Panicz Maciej Godek writes:
> I also used GOOPS, which I regret to this day, and so the
> whole framework needs a serious rewrite
What is it that you do not like about GOOPS? I have a project that may
be in the same position. I used GOOPS initially, then rewrote it to use
either GOOPS, plain li
>> If I understood Park SungMin right, the problem is rather with the
>> representation of a huge array as a list?
>
correct! (sorry..my poor english)
I think huge c-array should be representation as bytevector or pointer object.
(define type (list int (make-list 10 int)))
(define struct (mak
2016-03-30 13:18 GMT+02:00 Jan Nieuwenhuizen :
> Panicz Maciej Godek writes:
>
> > I also used GOOPS, which I regret to this day, and so the
> > whole framework needs a serious rewrite
>
> What is it that you do not like about GOOPS?
Most specifically, I dislike its middle three letters. The pro
Panicz Maciej Godek :
> 2016-03-30 13:18 GMT+02:00 Jan Nieuwenhuizen :
>
>> Panicz Maciej Godek writes:
>>
>> > I also used GOOPS, which I regret to this day, and so the
>> > whole framework needs a serious rewrite
>>
>> What is it that you do not like about GOOPS?
>
> Most specifically, I dislike
2016-03-30 19:53 GMT+02:00 Marko Rauhamaa :
> I like OOP, only I don't like GOOPS. Its classes and generic functions
> seem so idiomatically out of place, unschemish, if you will.
>
> This is how OOP ought to be done:
>
> https://www.gnu.org/software/guile/manual/html_node/OO-Closure.htm
> l#
On Wed, 30 Mar 2016, Marko Rauhamaa wrote:
Panicz Maciej Godek :
2016-03-30 13:18 GMT+02:00 Jan Nieuwenhuizen :
Panicz Maciej Godek writes:
I also used GOOPS, which I regret to this day, and so the
whole framework needs a serious rewrite
What is it that you do not like about GOOPS?
Mos
Park SungMin writes:
>>> If I understood Park SungMin right, the problem is rather with the
>>> representation of a huge array as a list?
>
> correct! (sorry..my poor english)
>
> I think huge c-array should be representation as bytevector or pointer
> object.
>
> (define type (list int (make-lis
Panicz Maciej Godek :
> 2016-03-30 19:53 GMT+02:00 Marko Rauhamaa :
> The problem with closures is, among others, that they are
> non-serializable
What is there to serialize in objects? How do you serialize a car? How
do you serialize an ant? How do you serialize a person?
All you can serialize
Jan Wedekind :
> GOOPS supports "open" classes and multiple-dispatch. E.g. you can extend
> the "write" method to control how an object is displayed within the
> Guile REPL [1]. Another interesting approach are multi-methods in
> Clojure which don't even require explicit types for dispatching.
>
>
On Wed, 30 Mar 2016, Marko Rauhamaa wrote:
Jan Wedekind :
GOOPS supports "open" classes and multiple-dispatch. E.g. you can extend
the "write" method to control how an object is displayed within the
Guile REPL [1]. Another interesting approach are multi-methods in
Clojure which don't even requ
Jan Wedekind :
> On Wed, 30 Mar 2016, Marko Rauhamaa wrote:
>> GOOPS' has the worst possible object model: objects are seen as mere
>> data records. The concept of a "slot" is an anathema to OOP.
>
> Ok, I have updated the example to use accessor functions instead of
> "slot-ref".
(get-x) is only
Thank you!! this library is very good solution for me!
It seems very useful.
> On Mar 31, 2016, at 4:54 AM, Taylan Ulrich Bayırlı/Kammer
> wrote:
>
> Park SungMin mailto:byulparan_...@icloud.com>>
> writes:
>
If I understood Park SungMin right, the problem is rather with the
repre
"Thompson, David" writes:
> The environment variable path separator is *not* defined depending on
> the OS.
Thank you for the clarification!
> Unless otherwise specified, the procedures/variables are in the
> default environment.
Ah, I see! Thank you.
--
Chris
signature.asc
Description: PG
16 matches
Mail list logo