From: Stephen Compall <s11@member.fsf.org>
Cc: guile-devel@gnu.org
Subject: Re: text buffers (was Re: Unicode and Guile)
Date: 04 Nov 2003 10:04:08 +0000 [thread overview]
Message-ID: <xfyznfc4fhj.fsf@csserver.evansville.edu> (raw)
In-Reply-To: <200311032034.MAA19395@morrowfield.regexps.com>
Tom Lord <lord@emf.net> writes:
> 1) buffers that aren't entirely memory resident but that are paged in
> "on demand" (for huge texts)
I did in fact think about these -- wrapping the buffer interface
around mmap, and abusing the gap seriously, maybe even making it a
separate buffer. I also thought about "read on demand", particularly
for network access, in which data won't be downloaded until its buffer
position or after is accessed. But if the class system won't allow
just anyone to do this cleanly, without cluttering the base
implementation (besides adding new hooks), then I won't look at it
again. Besides, as you said, it's not good to pursue such premature
optimization :)
--
Stephen Compall or s11 or sirian
If the meanings of "true" and "false" were switched, then this sentence
would not be false.
anarchy encryption Defcon Bellcore LABLINK UNSCOM Janet Reno Ron Brown
MP5K-SD colonel tempest Aldergrove fraud smuggle NORAD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-11-04 10:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 17:15 Unicode and Guile Andy Wingo
2003-10-25 17:08 ` Stephen Compall
2003-10-26 0:03 ` Tom Lord
2003-10-26 12:34 ` Which Encoding? (was Re: Unicode and Guile) Stephen Compall
2003-10-31 13:25 ` Unicode and Guile Andy Wingo
2003-11-03 13:35 ` text buffers (was Re: Unicode and Guile) Stephen Compall
2003-11-03 20:34 ` Tom Lord
2003-11-04 10:04 ` Stephen Compall [this message]
2003-11-03 20:31 ` Unicode and Guile Tom Lord
2003-11-06 18:16 ` Andy Wingo
2003-11-11 19:02 ` Tom Lord
2003-11-12 0:29 ` Marius Vollmer
2003-11-12 1:40 ` Tom Lord
2003-11-12 2:30 ` Marius Vollmer
2003-11-12 4:03 ` Tom Lord
2003-11-12 16:59 ` Marius Vollmer
2003-11-17 16:17 ` Andy Wingo
2003-11-12 0:06 ` Marius Vollmer
2003-11-12 1:27 ` Tom Lord
2003-10-31 13:16 ` Andy Wingo
2003-11-02 21:23 ` Kevin Ryde
2003-11-26 20:35 ` Mikael Djurfeldt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xfyznfc4fhj.fsf@csserver.evansville.edu \
--to=s11@member.fsf.org \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).