Hello,
Is there a way to get the memory usage of a datum?
(memory-usage abcdefg)
or
(memory-usage (lambda (n) (+ n 1)))
etc.
Ed
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
On 6/20/07, Eduardo Cavazos [EMAIL PROTECTED] wrote:
Hello,
Is there a way to get the memory usage of a datum?
(memory-usage abcdefg)
or
(memory-usage (lambda (n) (+ n 1)))
(##sys#size X) will return the number slots/words in a vector-like
object, or the number of bytes for a byte-vector
On 20 Jun 2007, at 3:12 am, Graham Fawcett wrote:
Since Chicken continuations are serializable, you could also store
them as values in the cache. Not sure of a use-case, but there you
are.
Interesting... Well, continuation-based web frameworks often want to
cache continuations. I'll have to
Ok, so that's one vote for separate 'memcached' and 'cache' eggs.
I would vote against a generically-named cache egg... There are many
types of caches (depending on storage medium, indexing, time
complexities of caching/retrieval, expiration strategies etc)
Best,
Dan
On 20 Jun 2007, at 10:04 am, felix winkelmann wrote:
(##sys#size X) will return the number slots/words in a vector-like
object, or the number of bytes for a byte-vector like object (i.e.
a string)
(It will crash for immediate data).
So I see:
#;3 (##sys#size 'foo)
2
#;4 (##sys#size 1)
Bus
On 6/20/07, Alaric Snell-Pym [EMAIL PROTECTED] wrote:
(It will crash for immediate data).
So I see:
#;3 (##sys#size 'foo)
2
#;4 (##sys#size 1)
Bus error
How many ways are there to crash a Chicken, actually?
Infinite.
(Cue why did the chicken cross the road jokes)
It'd be handy to have
On 20 Jun 2007, at 10:19 am, Dan Muresan wrote:
Ok, so that's one vote for separate 'memcached' and 'cache' eggs.
I would vote against a generically-named cache egg... There are
many types of caches (depending on storage medium, indexing, time
complexities of caching/retrieval, expiration
That's why my generic cache interface is intended to be a front-end
to different cache implementations, with a common interface, and some
tools built on top of that interface (such as memoizing functions).
Yes, I understand the philosophy, but before you can make a generic API,
one should
On 20 Jun 2007, at 11:05 am, Dan Muresan wrote:
That's why my generic cache interface is intended to be a front-end
to different cache implementations, with a common interface, and some
tools built on top of that interface (such as memoizing functions).
Yes, I understand the philosophy, but
I have improved on Graham Fawcett's wiki-texi conversion code in
stream-wiki, and now it is able to produce an almost usable Chicken
manual in Texinfo format.
Excellent! Thank you very much!
I just commited it, along with some tweaks, to the egg's trunk in the
Subversion repository.
1. All
10 matches
Mail list logo
