I will include a fix (and documentation) in the upcoming release.
On Sunday, November 20, 2022 2:24:24 AM PST JP de Vooght wrote:
> Thank you Taylor
>
> All good now with rb-tree/update! - I was skipping the microcode
> compilation phase.
>
> I use the source tarball, made by change to
It's not possible to advise compiled procedures. With some care, it's possible
to replace a particular procedure with an interpreted one. That involves
evaluating the source code of the procedure in the correct environment.
On May 13, 2022, 5:07 PM -0700, Sam Lee , wrote:
> Is it possible to use
They are in (mit legacy runtime).
On Dec 4, 2021, 6:01 AM -0800, Amirouche , wrote:
> In collusion with other people, I am trying to build a portable set of
> libraries.
>
> I started with a JSON library (rework of SRFI-180), the current test suite
> pass
> with nine Scheme implementation [0].
>
A lot of these issues are fixed in source but not yet released. You can build
from source if necessary.
On Dec 1, 2021, 10:46 AM -0800, Amirouche Boubekki
, wrote:
> > Also, it would be neat to have something like --library-extensions
> > option to override the default `.sld` and `.scm`
> >
> >
Yes, this is a known bug.
On Oct 10, 2021, 6:33 AM -0700, Tim Lee , wrote:
> I tried evaluate this expression found on page 32 of the R7RS-small
> standard:
>
> '#1=(a b . #1#)
>
> However, the datum label causes an error in MIT Scheme 11.2:
>
> ;Reference to non-shared object: #1#
>
> Is this a
I'm in favor of it meaning left shift, since that's what I've always thought it
was. I never make assumptions about what it does when shifting a negative
number to the right, but that's because I nearly always use it with nonnegative
numbers.
On Oct 30, 2020, 4:59 PM -0700, Taylor R Campbell
,
When cross compiling, aren’t they named .icb or something like that?
On Apr 30, 2020, 12:12 AM -0700, Taylor R Campbell , wrote:
> > Date: Wed, 29 Apr 2020 23:46:40 -0700
> > From: "Arthur A. Gleckler"
> >
> > *.bci files aren't installed when I do make install (sudo make install, in
> > fact). I
An easy way is to evaluate (environment-bound-names system-global-environment)
For undocumented procedures you’ll need to look in the sources. Start with
“src/runtime/runtime.pkg”, which contains most of the bindings going into the
global package. Look for clauses of the form (export () …), and
Look at src/runtime/runtime.pkg
All of the bindings are there, including special forms. You'll then find define
in mit-maxros.scm in the same directory.
On Apr 2, 2020, 9:36 PM -0700, Nicholas Papadonis
, wrote:
> How do I inspect the source code for special functions like (cond)?
>
> I tried
The read procedure is in the file “src/runtime/input-port.scm”; most of the
implementation is in “src/runtime/reader.scm”.
In general, to find a definition, look in “src/runtime/runtime.pkg” and search
for the name; the corresponding file will be shown in the package definition.
On Feb 20,
There are a handful of tests that fail on GNU/Linux and.Mac systems. I have a
to-do to look into this but haven't done anything about it.
On Jan 2, 2020, 1:47 PM -0500, David Liu , wrote:
> On Thu, Jan 2, 2020 at 1:25 PM Taylor R Campbell wrote:
> > > Try installing the ncurses development files
The nmv-header? problem should have been fixed. What version of Scheme are you
using?
On Dec 26, 2019, 1:03 PM -0500, David Liu , wrote:
> Ah great, applying that patch finally allowed psgo.scm to complete loading
> successfully, and it popped up three blank windows named g1, g2, and g3, as
>
[Trying again with correct email address.]
The nmv-header? problem should have been fixed. What version of Scheme are you
using?
On Dec 26, 2019, 1:03 PM -0500, David Liu , wrote:
> Ah great, applying that patch finally allowed psgo.scm to complete loading
> successfully, and it popped up three
parameterize doesn't exist in 9.1.1. There's an equivalent that can be
used with fluid-let but I don't remember the name offhand.
Using 10.1.10 would be preferable since it has much better standards
compliance.
On Sun, Sep 8, 2019 at 9:27 PM Taylor R Campbell
wrote:
> > Date: Mon, 9 Sep 2019
Yay!
FYI, I'm about to release 10.1.10, so if you need any last minute changes
let me know.
On Fri, Aug 9, 2019 at 10:11 PM Taylor R Campbell
wrote:
> I've confirmed that the closure rework branch I announced at hte
> beginning of the year can be built from 10.1.9 out of the box, so I'd
> like
pretty much any other
> language. So I have tried to find a solution by experimenting but that
> doesn't get me far. So I have to ask newb questions. If I ever get a hang
> on Scheme I would be pleased to write some tutorial.
>
> Kind regards
> Peter
>
> Chris Hanson schrieb
Please read the manual before asking this kind of question. Both your
question about the command line, and the other about compiling files, are
answered in the User's Manual.
The advice to use command-line-arguments is not useful here, because that
will only contain unknown arguments. Since
Cross compilation is not really working right in 10.1.*. It can be done but
it's complicated and whatever instructions you found are probably out of
date.
This has been cleaned up on HEAD but probably won't be released for a while.
On Thu, Feb 21, 2019 at 7:21 PM Duncan Mak wrote:
> Hello
Sorry for the long delay.
Please do this at your discretion. I am not actively working on anything
and will catch up when it's done.
On Mon, Jan 7, 2019 at 12:41 AM Taylor R Campbell
wrote:
> > Date: Sun, 6 Jan 2019 04:31:00 +
> > From: Taylor R Campbell
> >
> > > It sounds like this will
Should be fixed now.
On Fri, Mar 15, 2019 at 1:17 PM Chris Hanson wrote:
> Looks like the hack I put into the printer was a mistake.
> I'll fix it.
>
> On Thu, Mar 14, 2019 at 5:54 PM Matt Birkholz
> wrote:
>
>> I'm having fun with string slices except that they look li
Looks like the hack I put into the printer was a mistake.
I'll fix it.
On Thu, Mar 14, 2019 at 5:54 PM Matt Birkholz
wrote:
> I'm having fun with string slices except that they look like this:
>
> #[%record 42]
>
> The easiest way I've found to make them look like strings is this:
>
>
Fine with me. I have used it only for testing purposes, mostly because it's
so slow.
On Mon, Jan 21, 2019 at 3:48 PM Taylor R Campbell
wrote:
> In commit 1496f4c1d507dab5521309520de5c77ba3b5d82d, I changed the
> execute cache mechanism in SVM1 to be simpler, probably faster, and
>
MIT/GNU Scheme x11 plugin\""
> -DPACKAGE_TARNAME=\"mit-scheme-x11\" -DPACKAGE_VERSION=\"1.2\"
> "-DPACKAGE_STRING=\"MIT/GNU Scheme x11 plugin 1.2\"" -DPACKAGE_BUGREPORT=\"
> bug-mit-sch...@gnu.org\" -DPACKAGE_URL=\"\" -D
I'm going to put out a new bug-fix release this weekend, so please not
until that's finished.
Otherwise, just choose a day and let us know. And, of course, tell us how
to do the change since we'll each need to do this.
It sounds like this will break our rule about being able to build the next
done
On Tue, Dec 25, 2018 at 9:04 PM Taylor R Campbell
wrote:
> Can the data for this test be split out into a separate file that we
> read dynamically? The native i386 compiler chokes on this file
> because it's too large.
>
> ___
> MIT-Scheme-devel
Campbell
wrote:
> > Date: Sat, 8 Dec 2018 17:18:21 -0800
> > From: Chris Hanson
> >
> > I'm not using tags, just the separate branch for the release.
> >
> > The tags don't seem to add much value, and I don't think that use is what
> > they're mean
I'm not using tags, just the separate branch for the release.
The tags don't seem to add much value, and I don't think that use is what
they're meant for. And it's trivial to figure out what they would be from
the release changelogs.
I am considering making a new branch for 10.2.x and so on,
SGTM
On Sat, Dec 8, 2018 at 4:45 PM Taylor R Campbell
wrote:
> I brushed off the portable fasdumper I wrote a few years ago and added
> some tests, in the cross-fasdump-v2 branch.
>
> It seems to work for cross-compiling on amd64 for amd64, at least, and
> in principle it should work for any
On Tue, Nov 27, 2018 at 4:32 PM Taylor R Campbell
wrote:
> Stepping back a moment from file systems and on-disk vs in-memory
> caches, can you summarize the usage model of this?
>
> Here's some of the relevant operations that I want to be able to do,
> illustrated with how a C system would do it
I'm a little confused about what the problem is. Could you give specific
examples?
I'm also unsure about why having a file-system cache will help. Other than
persistence, what advantage does having the cache in the file system
provide? I can see an argument that the file system forces a
-0800
> > From: Chris Hanson
> >
> > Yeah, I'm puzzled by that one too. I didn't have time to chase it down
> > before the release.
>
> Seems to me the right thing to do is:
>
> 1. Invent FASL_ARCH_SVM1.
> 2. Teach the cross-compiler to spit it out.
>
> A
Yeah, I'm puzzled by that one too. I didn't have time to chase it down
before the release.
On Mon, Nov 12, 2018 at 9:49 PM Taylor R Campbell
wrote:
> If I try to run an svm1 binary build on a non-amd64 system when the
> .bin/.com/ files were built on amd64, it chokes on fasl arch
> mismatch.
>
Build the toolchain using 9.2 first, configuring with
--disable-default-plugins.
Then build the whole system from the toolchain, configuring with
--with-scheme-build=../toolchain (or whatever).
If you make source changes and want to update both, run make in the
toolchain build, then run it again
On Wed, Oct 24, 2018 at 7:12 PM Taylor R Campbell
wrote:
> > Date: Tue, 23 Oct 2018 14:47:07 -0700
> > From: Chris Hanson
> >
> > I just merged my makefile-refactor branch into master.
>
> Just tried ./Setup.sh && ./configure in a clean tree, and
>
>
I just merged my makefile-refactor branch into master.
The changes are pretty extensive:
- The "toolchain" compilation is gone, as is the bulk of the contents of
host-adapter. Compilation now makes a single pass through everything. In
general, cross compilation is now achieved by a
Yeah, it's been made into a separately configured add-on module.
I'm working on refactoring the Makefiles so that everything is built
correctly, but I'm not there yet.
If you need this done quickly then ask Matt what the right incantation is.
I think it's something like "run autogen.sh in each of
I'm in the process of putting together a new release of MIT/GNU Scheme.
Unfortunately, while most of out contributors have moved to 64-bit
hardware, the Windows port is still 32-bit. And it hasn't worked very well
in a long time, mostly because of memory addressing issues in the 32-bit
space.
I
This should be fixed now. It was dying due to a circular data structure --
which itself shouldn't have been printed.
But for future reference, if you think the thing you're printing may be
circular, do this:
(parameterize ((param:pp-avoid-circularity? #t)) (pp ...))
I'm open to arguments in
Use M-x font-apropos with an argument ".*" to see the available fonts.
Edwin doesn't support wildcards in fonts so you'll have to specify
everything.
On Sun, Mar 11, 2018 at 10:14 AM, Catonano wrote:
> I tried with this line in my .edwin file
>
> ((ref-command set-font)
Test failures due to unimplemented primitives, and places where values were
returned rather than traps thrown or vice versa.
On Fri, Nov 3, 2017 at 10:36 PM, Taylor R Campbell <campb...@mumble.net>
wrote:
> > Date: Fri, 3 Nov 2017 22:09:27 -0700
> > From: Chris Hanson <
I added some support for testing the existence of feenableexcept and
fedisableexcept, which are not part of C99 and not present in macOS.
I used this to disable tests that depend on their existence, which
otherwise failed.
Could you please check what I did and confirm that it is correct? I'm not
I'm happy to remove support for blowfish, mhash, and mcrypt. They were
reasonable choices at the time but that's at least 15-20 years ago now.
I'd like to retain support for MD5, however it's done. This is still useful
for non-cryptographic purposes.
On Fri, Nov 3, 2017 at 12:00 PM, Arthur A.
Do you have an X server installed?
On Jun 28, 2017 1:59 PM, "Aaron S. Hawley" wrote:
> > Just to clarify: when you say `interact with the REPL', are you
> > talking about the Edwin REPL or the console REPL?
>
> Well, one of the errors is Edwin failing to start
MIT/GNU Scheme has two major parts: the "microcode", written in C, and
everything else written in Scheme.
The unix distribution contains pre-compiled Scheme files, which depend only
on the processor architecture and not the operating system.
It also contains C source files, which depend on the
You could try changing the heap allocator to use malloc instead of mmap. On
a 64-bit architecture that should work fine.
On Fri, Jun 9, 2017 at 9:09 AM, Taylor R Campbell
wrote:
> > Date: Thu, 8 Jun 2017 18:04:45 -0400
> > From: Pavan Maddamsetti
I'd like to drastically reduce the number of parameters supported by the
parser and the unparser.
In particular I'd like to simplify them so that they are more closely
focused on reading and printing Scheme syntax, and not have so many bells
and whistles to allow them to be used for other
I just checked in a major refactor of the runtime system to have strings
with full Unicode support. See the commit logs, specifically the most
recent one, for more details.
There are probably many bugs in parts of the system that haven't been
converted to handle the new string type. I fixed all
If you look at the list archives you'll see that there's very little
traffic on this list.
On Dec 19, 2016 11:34 PM, "Steve Lett" wrote:
> Hi,
> It's been about 6 days since I signed up to this email and I haven't
> received a reply yet. Is this normal? Is there much
of empty vectors as eqv? is a valid point
of view, despite the standards. That said, our implementation should adhere
to the standards.
On Sun, Nov 6, 2016 at 5:11 AM, Alex Shinn <alexsh...@gmail.com> wrote:
> On Sat, Nov 5, 2016 at 6:29 PM, Chris Hanson <c...@chris-hanson.org> wr
I can understand why it acts that way, since two empty vectors are
equivalent for all intents and purposes.
Either way, eqv? and eqv-hash must agree, so one of them has to be changed.
The eqv? of empty vectors seems to be false according to R7RS. Except that
the section on eqv? is a little
Thanks, fixed.
On Tue, Mar 1, 2016 at 10:34 AM, wrote:
> > Fixed both bugs.
>
> One more, make check now fails on one test:
>
> ;Run tests "runtime/test-dynamic-env"...
> ; Generating "test-dynamic-env.bin" because of: "test-dynamic-env.scm"
> ; Generating SCode for file:
I've finished fixing the issues with parameters; all public parameters are
now called param:foo and each corresponds to the appropriate *foo*.
Most of these parameters are write-only from the user side, so I've bound
the *foo* variables to #!default and changed the code to pay attention only
when
Oops. I had generated my own TAGS file there and was surprised when it
tried to check it in. I should have looked at the original contents.
Go ahead and put it back.
On Feb 26, 2016 8:50 AM, "Arthur A. Gleckler" wrote:
> Hi, Chris. In change e0429c04, "TAGS shouldn't be in
Yes thanks.
On Feb 26, 2016 8:55 AM, "Arthur A. Gleckler" wrote:
> Hi, Chris. In change de2cb85c, "Put reduce-right back," you
> restored the implementation of `reduce-left' (not
> `reduce-right'). However, that change didn't restore the
> documentation for `reduce-left',
The current HEAD build breaks a lot of programs that work in 9.2.*
This is not acceptable; we can't just release stuff that breaks people's
programs without giving any kind of warning.
At a minimum, to make a significant change, the old behavior should be
maintained at least one release after
R7RS defines parameters, which we'll eventually need to implement anyway
for compliance. Converting the system's bindings over to parameters is
probably the right thing for a variety of reasons.
On Fri, Jan 17, 2014 at 5:49 AM, Taylor R Campbell campb...@mumble.netwrote:
Date: Thu, 16 Jan
What are you building from? The binary unix download?
On Mon, Nov 18, 2013 at 9:49 PM, Andrei Estioco chadesti...@gmail.comwrote:
Hi,
I'm trying to build MIT Scheme (9.1.1) under Ubuntu 12.04.3 64-bit.
However, running ./configure results to the following error:
checking for an existing
I updated the text as you suggest. I did not remove the 32-bit
qualifier because we have never done the work to support 64-bit
systems.
Thanks for the offer of a test system. I have a virtual machine
running Windows 7 that I use for generating the releases. What I
don't have access to is
I haven't. Here are the steps:
1. Make sure the copyrights are up to date; see dist/update-copyright.scm.
2. Run the various scripts in dist/ to create the necessary files.
The comments in each script say what dependencies it has, from which
you derive the necessary order; IIRC make-src-files
This only makes sense when being run in the background. By all means
don't detach otherwise.
On Wed, May 29, 2013 at 8:03 AM, Taylor R Campbell campb...@mumble.net wrote:
Does anyone rely on Scheme's behaviour of detaching from the ctty in
batch mode or when file descriptors 0/1/2 are not
Actually the correct fix is
(let ((input (open-input-octets octets start end)))
which I've committed to HEAD.
On Thu, May 3, 2012 at 1:53 AM, cra...@gmx.net wrote:
On Wed, 2 May 2012 22:44:44 -0700, Chris Hanson c...@chris-hanson.org wrote:
You're confused because URL:ENCODE-STRING has
You're confused because URL:ENCODE-STRING has nothing to do with url
encoding, which the encoding used for
application/x-www-form-urlencoded (and which itself has nothing to do
with URIs).
As the code comment says, this is just a backwards compatibility
procedure for something that existed in the
I've fixed this in the source (attached).
2012/3/25 Frank eular.fr...@gmail.com:
When any error occurs, after putting ,a, the source code window doesn't
resume.
And tab completion doesn't work well.
To MIT-Scheme developer: It might be a bug in MIT-Scheme.
Error occurs
The object nil,
Only the 9.1 release has any Slime support. I haven't had time to do
more work on it, but the code in that release does work.
On Tue, Mar 20, 2012 at 4:27 AM, Frank eular.fr...@gmail.com wrote:
于 2012年03月20日 19:06, Tamás Kovács 写道:
I see, thanks.
Do you know a way how to detect whether the
Woohoo
Thanks Matt. I'll try it out later tonight.
On Thu, Mar 8, 2012 at 4:20 PM, Matt Birkholz
m...@birkholz.chandler.az.us wrote:
Bless me, Schemers, for I have Schemed.
It has been 10 months since my last confession and, with a little help
from my friends, we now have a working,
I made this change because a user reported that the code failed to
compile in slackware when both were included.
Is there a use case where both must be included? Or should I just
change it to prefer termcap.h over term.h?
On Mon, Mar 5, 2012 at 11:24 AM, Taylor R Campbell campb...@mumble.net
Should be fixed now.
On Fri, Nov 18, 2011 at 5:20 AM, Margherita Pizza
terremotoetrage...@gmail.com wrote:
Hi. In this page:
http://www.gnu.org/software/mit-scheme/
This link is broken:
http://ftp.gnu.org/gnu/mit-scheme/stable.pkg/9.1.1/mit-scheme-9.1.1-i386-win32.exe
Seems pretty
Should be fixed now.
On Wed, Nov 23, 2011 at 1:31 AM, Jose Grimaldo josegrima...@gmail.com wrote:
Hello
The link for windows is broken
http://www.gnu.org/software/mit-scheme/
___
MIT-Scheme-devel mailing list
MIT-Scheme-devel@gnu.org
Before compiling on Mac OS X you need to have XCode installed first.
On Wed, Nov 23, 2011 at 3:04 AM, Visar Zejnullahu
visar.zejnull...@gmail.com wrote:
This might be more up-to-date:
http://www.gnu.org/software/mit-scheme/documentation/mit-scheme-user/Starting-Edwin.html
I tried
OK, I've built a new release (9.1.1) that incorporates my float-env
patch as well as support for plain make in the native-code release
downloads.
Hopefully this will avoid further problems in the future.
Huston, thanks for reporting this.
On Tue, Nov 8, 2011 at 3:07 PM, Matt Birkholz
LGTM
Do you want to update the release notes page, or shall I?
On Tue, Oct 18, 2011 at 8:21 PM, Taylor R Campbell campb...@mumble.net wrote:
I scanned the commits between 9.0.1 and 9.1 (approximately, since we
don't currently use tags to identify them), and wrote up some brief
release notes.
OK, no problem.
On Wed, Oct 19, 2011 at 7:22 AM, Taylor R Campbell campb...@mumble.net wrote:
Date: Wed, 19 Oct 2011 01:01:58 -0700
From: Chris Hanson c...@chris-hanson.org
Do you want to update the release notes page, or shall I?
I suspect neither of us is privy to any sources
Done. Thanks for writing them up.
On Wed, Oct 19, 2011 at 12:50 PM, Chris Hanson c...@chris-hanson.org wrote:
OK, no problem.
On Wed, Oct 19, 2011 at 7:22 AM, Taylor R Campbell campb...@mumble.net
wrote:
Date: Wed, 19 Oct 2011 01:01:58 -0700
From: Chris Hanson c...@chris-hanson.org
I don't understand why this is needed. I regularly use the same
binary from the command line and from an application. The only
difference is that I install the command-line code in /usr/local/bin
and the library in /usr/local/lib/mit-scheme-x86-64. Is this because
you're trying to run this code
Sounds fine to me.
On Fri, Aug 13, 2010 at 4:27 PM, Taylor R Campbell campb...@mumble.net wrote:
I'd like to add a procedure called REFERENCE-BARRIER to the system.
(REFERENCE-BARRIER x) has the consequence that whatever the value of
x, the garbage collector must not reclaim the storage of
In cases like these I prefer a small number of very general
definitions, so I'd favor having all the options be defined as
arguments. Provided, of course, that there are compatibility bindings
for existing usage.
On Sat, Aug 14, 2010 at 8:12 PM, Taylor R Campbell campb...@mumble.net wrote:
Yes, by all means get rid of them.
On Sat, Aug 7, 2010 at 7:44 PM, Taylor R Campbell campb...@mumble.net wrote:
The archaic state space primitives are not only archaic but apparently
completely broken too:
((make-primitive-procedure 'execute-at-new-state-point 4)
#f (lambda () 0) (lambda ()
Thanks; that was the problem. Fixed in git.
On Sat, Apr 24, 2010 at 1:01 PM, Taylor R Campbell campb...@mumble.net wrote:
Date: Sat, 24 Apr 2010 12:17:15 -0700
From: Chris Hanson c...@chris-hanson.org
There's a reproducible bug in Edwin that appears to be a compiler bug
in the x86
The new SF is generating unreferenced bound variables in situations
where the variables are referenced. In the two cases I looked at,
both involved conditionals in which the variable was referenced on one
arm of the conditional but not the other.
___
This should be a per-file option; it's a syntactic hack. Instead of
having a global option, invent some kind of # syntax to say what the
keyword syntax is. This is how case sensitivity should be handled as
well, IMO.
On Mon, Mar 15, 2010 at 3:00 PM, Joe Marshall jmarsh...@alum.mit.edu wrote:
a standard mechanism for doing any of
this. But there should be. Want to implement one?
On Mon, Mar 15, 2010 at 4:13 PM, Joe Marshall jmarsh...@alum.mit.edu wrote:
On Mon, Mar 15, 2010 at 3:14 PM, Chris Hanson c...@chris-hanson.org wrote:
This should be a per-file option; it's a syntactic
On Mon, Mar 15, 2010 at 5:16 PM, Joe Marshall jmarsh...@alum.mit.edu wrote:
On Mon, Mar 15, 2010 at 4:57 PM, Chris Hanson c...@chris-hanson.org wrote:
In which case READ should be told what it is supposed to do, or the
thing you're reading should also be marked.
The syntax marker isn't a per
The main issue with that is to keep a reverse map around so that
debugging can show the original variable names. Right now the
debugger just shows the scode, which works only because we don't
alpha-rename everything.
On Mon, Jan 25, 2010 at 2:11 PM, Taylor R Campbell campb...@mumble.net wrote:
I have Snow Leopard but haven't yet tried it. I'll give it a try
later tonight if I have the energy.
On Tue, Dec 8, 2009 at 4:52 PM, Arthur A. Gleckler a...@speechcode.com wrote:
By the way, if your goal is just to build the latest Scheme, you can
start with
Might be nice to have the benchmark in the tests directory.
On Wed, Nov 25, 2009 at 3:19 PM, Joe Marshall jmarsh...@alum.mit.edu wrote:
Just pushed a few more changes. I wrote a simple benchmark which just
involved reading 97800 symbols from a file. (The symbols were already
interned).
2009 13:17:49 -0800
From: Chris Hanson c...@chris-hanson.org
I've pushed some OS X changes to git, but I still haven't got a
working compile.
The current problem I'm looking at is this:
./makegen/m4.sh cmpauxmd.m4 cmpauxmd.s
as -arch x86_64 -o cmpauxmd.o cmpauxmd.s
cmpaux-x86
That case isn't such a big deal, but the general string-accumulator
pattern gets used in a bunch of places where the overhead is very low,
such as in utf-8 conversion. I'd like to be able to use string-head!
there too.
On Thu, Sep 24, 2009 at 1:48 PM, Joe Marshall jmarsh...@alum.mit.edu wrote:
But clearly _you_ know the definition of 'sarcasm'. :)
On Mon, Sep 21, 2009 at 12:44 PM, Joe Marshall jmarsh...@alum.mit.edu wrote:
On Mon, Sep 21, 2009 at 12:03 PM, Chris Hanson c...@chris-hanson.org wrote:
Joe, you want to give this a try in your copious free time? I think
you could have
I don't understand how you concluded that the reordering algorithm
won't do anything.
In any case, I am ambivalent about the approach taken.
On Mon, Sep 21, 2009 at 2:37 PM, Taylor R Campbell campb...@mumble.net wrote:
Any preference now about which transformation to commit, between the
.
On Sun, Sep 20, 2009 at 7:54 AM, Taylor R Campbell campb...@mumble.net wrote:
Date: Sat, 19 Sep 2009 22:58:20 -0700
From: Chris Hanson c...@chris-hanson.org
This looks OK, though it seems excessively conservative. You're doing
[snip]
but only in certain restricted cases. I am
Arggh Good catch. Let's move the transcript operations as you suggest.
On Sun, Sep 20, 2009 at 12:14 PM, Joe Marshall jmarsh...@alum.mit.edu wrote:
On Sat, Sep 19, 2009 at 9:50 PM, Taylor R Campbell campb...@mumble.net
wrote:
For SYMBOL?, I thought it was worth integrating because
It's worth the trouble in some situations. Generally I only use it
when the parameters are referred to exactly once, or when I know that
the arguments are always simple expressions without side effects.
There is code in the compiler to optimize expressions of the form
((lambda (x) ...) y), but
Something to keep in mind is that define-integrable normally has no
effect outside of the file that it appears in. It's rare for someone
to use the integrate-external declaration.
On Sat, Sep 19, 2009 at 3:37 PM, Joe Marshall jmarsh...@alum.mit.edu wrote:
On Sat, Sep 19, 2009 at 3:27 PM, Taylor
This looks OK, though it seems excessively conservative. You're doing
((let ((a (foo)) (b (bar)))
(lambda (receiver)
...body...))
(lambda (x y z) ...))
=
(let ((receiver (lambda (x y z) ...)))
(let ((a (foo)) (b (bar)))
...body...))
but only in
FYI, while testing my most recent changes, I ran across a recent
compiler bug. To reproduce: using the current compiler, do a fresh
compile from sources. Then use that compiler to do another fresh
compile. The second compilation hangs during the compilation of
cref/anfile (the very first file
Yeah, I'm running a test now starting from the 20090107 binary and
compiling sources from head, and the second compilation is going fine.
I'm wondering if there's something wrong with my current binary (and
how that could happen).
On Fri, Sep 18, 2009 at 3:16 PM, Taylor R Campbell
My mistake: I forgot I was testing the sources from commit
3b5c6a1def63320a24c45294afa873fde9194625. They appear to be fine.
I'm now running the same test on HEAD.
On Fri, Sep 18, 2009 at 3:24 PM, Chris Hanson c...@chris-hanson.org wrote:
Yeah, I'm running a test now starting from the 20090107
Not sure about that. I'm doing the bisection now. The bug isn't
present in commit 745a16218a43692d2c9ecdad72d1bab73fab0522 from Sept.
7, so it's pretty recent.
On Fri, Sep 18, 2009 at 8:35 PM, Joe Marshall jmarsh...@alum.mit.edu wrote:
On Fri, Sep 18, 2009 at 1:57 PM, Chris Hanson c...@chris
Sounds good, but use DEFINE-INTEGRABLE instead of the declaration. It
will do a slightly better job.
On Thu, Sep 10, 2009 at 8:06 AM, Joe Marshall jmarsh...@alum.mit.edu wrote:
I have two changes I'll push this afternoon if no one objects.
1. (declare (integrate-operator symbol?)) in
LGTM. Can I suggest you order the procedures as per the attached?
On Sun, Sep 6, 2009 at 10:06 AM, Joe Marshalljmarsh...@alum.mit.edu wrote:
Hello cph,
I'd like you do a code review
(declare (integrate-operator %string-head))
(define (%string-head string end)
(%substring string 0
1 - 100 of 135 matches
Mail list logo