Re: unsigned-int

2017-06-22 Thread Catonano
For now I renounced to extract numbers from my bytevectors The culprit is: #vu8(232 3 0 0) There are 27 lines in the sheet, so this bytevector should represent 27, somehow. The good bytevector is: #vu8(5 0) In fact, the sheet has 5 columns On another sheet in the same file, this is what happe

Re: unsigned-int

2017-06-22 Thread Catonano
2017-06-22 21:55 GMT+02:00 Catonano : > 2017-06-22 21:33 GMT+02:00 Catonano : > >> 2017-06-22 21:13 GMT+02:00 Catonano : >> > >> > >> > I apologize if my questions are naive. >> > I wrote my last scrap of C code in about 2004 and it never was my thing >> > Also the manual is a great reference but

Re: unsigned-int

2017-06-22 Thread Catonano
2017-06-22 21:33 GMT+02:00 Catonano : > 2017-06-22 21:13 GMT+02:00 Catonano : > > > > > > I apologize if my questions are naive. > > I wrote my last scrap of C code in about 2004 and it never was my thing > > Also the manual is a great reference but not a great tutorial and I'm > not a great reade

Re: unsigned-int

2017-06-22 Thread Catonano
2017-06-22 21:13 GMT+02:00 Catonano : > > > I apologize if my questions are naive. > I wrote my last scrap of C code in about 2004 and it never was my thing > Also the manual is a great reference but not a great tutorial and I'm not a great reader, probably. Something that is concerning me is that

Re: unsigned-int

2017-06-22 Thread Catonano
2017-06-22 18:20 GMT+02:00 Mark H Weaver : > Catonano writes: > > > I can't extract correct values from unsigned-int's > > > > I can extract correct values from int, unsigned-short > > > > but NOT form an unsigned-int > > > > In that case the number that comes out is plainly wrong > > > > This is

Re: read syntax vectors immutable

2017-06-22 Thread Mark H Weaver
I wrote: > To create a mutable vector, use 'vector', or apply 'vector-copy' to a > literal vector. Also note that these are shallow copies, e.g. if you > have nested vector literals, 'vector-copy' will only copy the top layer. 'make-vector' is also useful for many purposes. Mark

Re: read syntax vectors immutable

2017-06-22 Thread Mark H Weaver
j kalbhenn writes: > vectors created using read syntax are apparently immutable with guile 2.2.2: > > -- > (define a #(0)) > (if (vector? a) (vector-set! a 0 1)) > > In procedure vector-set!: Wrong type argument in position 1 (expecting > mutable vector): #(0) > -- > > is this documented somewhe

Re: unsigned-int

2017-06-22 Thread Mark H Weaver
Catonano writes: > I can't extract correct values from unsigned-int's > > I can extract correct values from int, unsigned-short > > but NOT form an unsigned-int > > In that case the number that comes out is plainly wrong > > This is how I extract a number from an int (and it works) > > (bytevecto

Re: unsigned-int

2017-06-22 Thread Catonano
The relevant code is here https://gitlab.com/humanitiesNerd/guile-freexl/blob/master/freexl/common.scm and the not working function is "freexl-worksheet-dimensions" on line 132

unsigned-int

2017-06-22 Thread Catonano
I can't extract correct values from unsigned-int's I can extract correct values from int, unsigned-short but NOT form an unsigned-int In that case the number that comes out is plainly wrong This is how I extract a number from an int (and it works) (bytevector-uint-ref (pointer->bytevector

legacy object properties

2017-06-22 Thread Ernest Adrogué
Hi, The Reference Manual documents a number of procedures for handling object properties based on association lists (https://www.gnu.org/software/guile/manual/html_node/Object-Properties.html). However it says: “this is a legacy interface; you should use weak hash tables or object properties inste

read syntax vectors immutable

2017-06-22 Thread j kalbhenn
vectors created using read syntax are apparently immutable with guile 2.2.2: -- (define a #(0)) (if (vector? a) (vector-set! a 0 1)) In procedure vector-set!: Wrong type argument in position 1 (expecting mutable vector): #(0) -- is this documented somewhere in the guile manual or part of the sc