headers
Ivan Shmakov | 8 Sep 2008 11:45
Picon
Gravatar

Re: a Scheme48 wrapper for Sqlite3

>>>>> "IS" == Ivan Shmakov <ivan <at> theory.asu.ru> writes:

 IS> I've made some changes to the code, but I'm currently too busy to
 IS> finish the work.  I'm therefore posting the code in its current
 IS> state in the hope that it might be useful to someone.

	I've reworked the code a bit, and the user-visible changes are
	roughly as follows.

    * The code is now rewritten to utilize the new Scheme48 FFI (for
      to-be Scheme 1.9.)

    * The error-signalling variants are now provided for a number of
      functions; these variants are: `sqlite3-open', `sqlite3-close',
      `sqlite3-prepare-2', `sqlite3-prepare',
      `sqlite3-prepared-finalize!', `sqlite3-prepared-reset!',
      `sqlite3-prepared-step!'.

    * The interfaces were extended by `sqlite3-column-name' (with error
      signalling) and `sqlite3-column-name-1' (without), mostly to allow
      for `sqlite3-exec' to be reimplemented.

    * The `sqlite3-exec' is now reimplemented on top of the rest of the
      interface; both `sqlite3-exec-1' and sqlite3_s48_exec () are gone.

    * An example makefile is provided.

	I've tested it with Scheme48 (as of [1]), and it appears to
	build and work correctly:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ivan Shmakov | 13 Sep 2008 23:48
Picon

Re: SIGSEGV trying to bootstrap Scheme48 from VCS

>>>>> Michael Sperber <sperber <at> deinprogramm.de> writes:

 >>>>> How did you build the running Scheme 48 from the development code
 >>>>> itself?

 >>>> The same way as I've tried to build the development version of
 >>>> Scheme48 with itself later (already posted to this thread), only
 >>>> using Scheme48 1.8 as the basis.

[...]

 >>> So *how* did you build the development version that crashed? :-)

 >> I guess, I'm now the one confused with the question.

 >> The development code that crashed was built the way just like the
 >> one I've used to build the development code with itself, i. e.:

 > I think I somehow got into a mind state where I believed you're doing
 > all of this on Windows: sorry about that.  On what platform are you
 > doing it?

	I do it on GNU/Linux, as of Debian Etch (amd64 port.)

	As I was suspicious about possible bugs within the new FFI
	(well, what's the most likely place for bugs which lead to
	segmentation faults, anyway?), I've build Scheme48 as of
	6ab92621cc7c [1].  It wasn't a big surprise that /that/ version
	did indeed compile itself fine.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Ivan Shmakov | 14 Sep 2008 16:54
Picon

Re: SIGSEGV trying to bootstrap Scheme48 from VCS

>>>>> Michael Sperber <sperber <at> deinprogramm.de> writes:

 >> Perhaps the runtime and PreScheme compiler are not quite in sync in
 >> the latest hg?  I could be wrong, but it seems like in general one
 >> would build the development system with a stable version of the
 >> compiler (unless one were working on the compiler of said
 >> development system).

 > In principle, it should work, but it's not the usual mode of
 > operation of the developers.  I'll check it out.

	Actually, I'd expect that any revision should be able to build
	itself in full.  Besides, isn't such a build a good test for the
	system?

	Therefore, I'd suggest to include (re)building of the essential
	parts (such as initial images and the C code) as part of the
	Make `test' target.  The resulting files should then match
	byte-wise those supplied with the release.

	It may make sense to include $ make test as the final step of $
	make enough (unless disabled by the user), and to fail on the $
	make install stage if such a test wasn't passed (nor disabled by
	the user.)
Permalink | Reply | 0 comments |
headers
Marcus Crestani | 22 Sep 2008 23:39
Picon

Re: SIGSEGV trying to bootstrap Scheme48 from VCS

>>>>>"IS" == Ivan Shmakov <ivan <at> theory.asu.ru> writes:
>>> The development code that crashed was built the way just like the
>>> one I've used to build the development code with itself, i. e.:

>> I think I somehow got into a mind state where I believed you're doing
>> all of this on Windows: sorry about that.  On what platform are you
>> doing it?

IS> 	I do it on GNU/Linux, as of Debian Etch (amd64 port.)

Ivan, do you still see this problem with the current development sources
(5f5e619749e0)?  I was not able to reproduce the error on either

Linux galibier 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 12:38:37 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux

and

Darwin izoard 9.5.0 Darwin Kernel Version 9.5.0: Wed Sep  3 11:29:43 PDT 2008;
root:xnu-1228.7.58~1/RELEASE_I386 i386.

--

-- 
Marcus
Permalink | Reply | 1 comment |
headers
Mitchell Wand | 24 Sep 2008 07:16
Favicon

[Scheme Steering Committee announcements] Scheme Language Steering Committee election: preliminary announcement

The current Scheme Language Steering Committee was appointed in
January, 2004.  We have seen the Scheme Standardization process, as
envisioned in the charter from November, 2003, through to the ratification
of the R6RS in 2007. 

We believe that the R6RS is not the end of the Scheme language
standardization process, and that the Scheme language must continue to
evolve.

However, it was never our intention to be "Scheme Czars for Life."  It is
time to turn the process over to other hands, so that the Scheme
language will remain alive and healthy for years to come.

The Scheme Standardization Charter says, "The Steering Committee
itself shall establish procedures for replacing its members."  It is
therefore our intention to hold an election to replace ourselves.

Our plan is to publish a detailed plan and have a period for comments
on the plan, as we did for the ratification process.

I announced this at the Scheme Workshop in Victoria, British
Columbia on 9/20/08, so I am announcing it to this list now.  We still
have a few details to iron out (and I'm travelling for the next
several weeks), so I expect the draft plan and official opening of the
comment period to take place sometime in October.

The mailing list r6rs-discuss <at> lists.r6rs.org is open now for discussion on this topic.

For Alan and Guy,
--Mitch Wand



_______________________________________________
Scheme-announcements mailing list
Scheme-announcements <at> lists.ccs.neu.edu
https://lists.ccs.neu.edu/bin/listinfo/scheme-announcements
Permalink | Reply | 0 comments |
headers
Ivan Shmakov | 30 Sep 2008 19:04
Picon

no more SIGSEGV when trying to bootstrap Scheme48 from VCS

>>>>> "MC" == Marcus Crestani <crestani <at> informatik.uni-tuebingen.de> writes:
>>>>> "IS" == Ivan Shmakov <ivan <at> theory.asu.ru> writes:

 IS> The development code that crashed was built the way just like the
 IS> one I've used to build the development code with itself, i. e.:

 MS> I think I somehow got into a mind state where I believed you're
 MS> doing all of this on Windows: sorry about that.  On what platform
 MS> are you doing it?

 IS> I do it on GNU/Linux, as of Debian Etch (amd64 port.)

 MC> Ivan, do you still see this problem with the current development
 MC> sources (5f5e619749e0)?

	I've just built initial.images of f6856f11c6f34 with
	6ab92621cc7c, and then again, with itself -- it built just fine,
	with the images matching bytewise:

$ sha1sum build/initial.image-* 
a27bb81b8ceea2fe999382e8e80d15ae60894e11  build/initial.image-32
a27bb81b8ceea2fe999382e8e80d15ae60894e11  build/initial.image-32.old
658ba49dc83a15fce804c0cab19d623d35dd2eb8  build/initial.image-64
658ba49dc83a15fce804c0cab19d623d35dd2eb8  build/initial.image-64.old
$ 

	Thanks!

	I still wonder, how difficult would it be to make initial.images
	building a part of the (IIUC, non-existing, as of yet) test
	suite?

[...]
Permalink | Reply | 0 comments |

Gmane