Gambit-modules-list Avril 2009

gambit-modules-list@iro.umontreal.ca

6 participants
4 discussions

Does Black Hole export C type definitions just like it does with
by Mikael More 30 Avr '09

30 Avr '09

Per, I have a vague memory that when I checked the most previous time, when in module A I declared a particular C type, and in module B I had a C FFI definition that made use of that type (for argument or return value), I needed to redefine the C type in module B. How is it nowadays? Are there any risks involved in this, such as that the one and same C type, as created by FFI routines in module A and B, could somehow appear as made of two different types, or that they would somehow be incompatible with each others? Mikael

3 2

Ann.: CHICKEN 4.0.0 - comp.lang.scheme | Google Groups
by Bradley Lucier 06 Avr '09

06 Avr '09

Note particularly: - The macro system has been completely rewritten and is now fully hygienic with highlevel R5RS "syntax-rules" macros and low level "explicit renaming" macros that allow full control over hygiene; "define-macro" is not available anymore - A module system has been implemented that fully supports hygienic macros and integrates with separate and cross compilation; module- and syntax meta-information is not retained in compiled run-time code, unless explicitly enabled by the user - Experimental support for cross-module inlining http://groups.google.com/group/comp.lang.scheme/browse_thread/thread/ 3d248d275f929b97#

1 0

Re: [Gambit-modules-list] Syntactic tower
by Marc Feeley 03 Avr '09

03 Avr '09

On 2-Apr-09, at 4:25 PM, Per Eckerdal wrote: > But I still don't see any error in the main point of my previous > mail, that is that only two different sets of globals are needed. No... that's wrong. In the tower model each instance is an independent cell. If one of the levels is keeping state in one of these cells, you don't want it to interfere with the state in another cell (i.e. for the same variable at a different level). Keeping state is useful at the macro expansion level to keep tables of macros you have seen in the file being expanded. State is not the only thing... you might store in a module's variable "v" some information which will not be the same at all levels (a timestamp, a data structure, a list, etc). So you can't get out of this trouble by ordering the initializations. Marc

2 4

Syntactic tower
by Per Eckerdal 02 Avr '09

02 Avr '09

Hello again. I have been thinking about how to implement the syntactic tower in a simple but correct way. What I have come up with is this: In a module, there are different environments, one for each different phase of evaluation (runtime, macro expansion time, macro macro expansion time and so on). (This is not a new invention in any way. I just hope that I have copied the concepts correctly.) If you write normal code with no macros, only environment with phase 0 is into play. You get into the next phase in macro definitions or by using the syntax-begin form: (import srfi-1) (syntax-begin (import srfi-13)) (define (a-function) ;; This is inside environment phase 0. ;; Things from srfi-1 are available, but not things from srfi-13. fold) (define-macro (a-macro) ;; Because this is macro definition, this is inside environment phase 1. ;; Things from srfi-13 are available, but not things from srfi-1 (define-macro (an-inner-macro) ;; This is inside environment phase 2. ;; Neither srfi-1 nor srfi-13 are imported in this environment. "hello world") (string-titlecase (an-inner-macro))) The module system's runtime functions (for instance expand-macro and syntax-rules) are available at the REPL and at all environments whose phase >= 1. It's possible to use the module system's runtime in modules' functions, but then you have to explicitly import the module system. This is to make it clear that unless explicitly noted, compiled code is not dependent on the module system. This also makes it easier to tell which modules need to be loaded when compiling a module. Does this make sense? Or am I trying to solve a non-problem? Is this overly difficult to understand? /Per

4 11

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Gambit-modules-list Avril 2009