Hi,
On linux, x86-64 I can now write,
(use-modules (native aschm))
(define b (asm
(inst mov rbx 10) ;rbx = 1000,000,000
loop:
(inst cmp rbx 0)
(inst jmp #:eq out:)
(inst dec rbx)
(inst jmp loop:)
out:
(
Krister Svanlund writes:
> On Sat, Jun 9, 2012 at 2:32 PM, David Kastrup wrote:
>
>
> One principal distinguishing feature, like with a Scheme
> hashtable, is the ability to grow on-demand.
>
> Scheme/Guile vectors are fixed size.
>
> It is a bit of a nuisance that one can g
Hello,
On Sat 09 Jun 2012 17:16, Thien-Thi Nguyen writes:
> If you want to make a case for such a facility, why not
> show some code, both without (status quo) and with (proposed)?
> It should be clear what expressiveness is gained, and how.
For example, let's say I mmap a big file.
(define
() Andy Wingo
() Sat, 09 Jun 2012 13:07:15 +0200
Again, the gain in expressiveness is probably worth it
Overall, i am concerned about quick fixes and slow suffering
in the Guile design. To break it down from different angles:
Thinking positively:
If you want to make a case for such a facil
On Sat, Jun 9, 2012 at 2:32 PM, David Kastrup wrote:
>
> Hi,
>
> the main data structure of Lua is a "table", an associative array, and a
> table t has a continguous numerically addressed part from 1..#t, with
> all other indices going through a hashing mechanism. One principal
> distinguishing
Hi,
It would be very convenient to offer bytevectors that give a view on
some other data structure, possibly another bytevector. We already have
that, to an extent, with pointer->bytevector. We can consecrate that
with some subbytevector facility.
I think it's a good idea but it has some costs.
Hi,
the main data structure of Lua is a "table", an associative array, and a
table t has a continguous numerically addressed part from 1..#t, with
all other indices going through a hashing mechanism. One principal
distinguishing feature, like with a Scheme hashtable, is the ability to
grow on-de
Hi,
On Sat 09 Jun 2012 05:01, "B.Tag" writes:
> ok.
> i system environmental path included chinese.compile time it does not
> understand Chinese.
Interesting! I'm happy it worked for you, but I am curious what the
precise error was. Which environment variable caused the build to fail?
Th
