This site is a static rendering of the Trac instance that was used by R7RS-WG1 for its work on R7RS-small (PDF), which was ratified in 2013. For more information, see Home.

Source for ticket #46

cc


    

changetime

2010-10-18 11:29:27

component

WG2 - Control

description

Is there some proposal available for having interrupts in the core language ?

This is really needed for system programming or scheduling.

id

46

keywords


    

milestone


    

owner

cowan

priority

major

reporter

medernac

resolution

duplicate

severity


    

status

closed

summary

Interrupts

time

2010-03-17 14:44:42

type

defect

Changes

Change at time 2010-10-18 11:29:27

author

cowan

field

comment

newvalue

Migrated to WG2 docket.

oldvalue

5

raw-time

1287376167000000

ticket

46

time

2010-10-18 11:29:27

Change at time 2010-10-18 11:29:27

author

cowan

field

description

newvalue

Is there some proposal available for having interrupts in the core language ?

This is really needed for system programming or scheduling.

oldvalue

Is there some proposal available for having interrupts in the core language ?

This is really needed for system programming or scheduling.

raw-time

1287376167000000

ticket

46

time

2010-10-18 11:29:27

Change at time 2010-10-18 11:29:27

author

cowan

field

resolution

newvalue

duplicate

oldvalue


    

raw-time

1287376167000000

ticket

46

time

2010-10-18 11:29:27

Change at time 2010-10-18 11:29:27

author

cowan

field

status

newvalue

closed

oldvalue

new

raw-time

1287376167000000

ticket

46

time

2010-10-18 11:29:27

Change at time 2010-03-31 14:56:01

author

medernac

field

comment

newvalue

Replying to [comment:3 arcfide]:
> http://www.scheme.com/csug8/control.html#./control:h4

Thanks for the link, 

Indeed Chez Scheme provides a nice approach to [http://www.scheme.com/csug8/system.html#SECTSYSTEMINTERRUPTS Interrupts].  
I would like to generalize it to other signals handling, WG2 is maybe the more appropriate place for all this features, as you said, however I don't see how to implement real timing interrupts on top of WG1 from now with continuations only. Sure engines provide abstract time with "fuel", but this is not real timing.

oldvalue

3.4

raw-time

1270022161000000

ticket

46

time

2010-03-31 14:56:01

Change at time 2010-03-31 14:56:01

author

medernac

field

component

newvalue

WG2 - Control

oldvalue

WG1 - Core

raw-time

1270022161000000

ticket

46

time

2010-03-31 14:56:01

Change at time 2010-03-31 14:56:01

author

medernac

field

owner

newvalue

cowan

oldvalue

alexshinn

raw-time

1270022161000000

ticket

46

time

2010-03-31 14:56:01

Change at time 2010-03-20 10:44:08

author

arcfide

field

comment

newvalue

http://www.scheme.com/csug8/control.html#./control:h4

oldvalue

3

raw-time

1269056648000000

ticket

46

time

2010-03-20 10:44:08

Change at time 2010-03-19 16:56:38

author

medernac

field

comment

newvalue

Replying to [comment:1 arcfide]:
> I think that engines are a good candidate for this sort of thing, but I'm not inclined to include them in the core language.

Do you have some references about this and interrupts, please ?

I thought about Unix signals like handling and specially about timers. 

oldvalue

1.2

raw-time

1268992598000000

ticket

46

time

2010-03-19 16:56:38

Change at time 2010-03-18 11:04:00

author

arcfide

field

comment

newvalue

I think that engines are a good candidate for this sort of thing, but I'm not inclined to include them in the core language.

oldvalue

1

raw-time

1268885040000000

ticket

46

time

2010-03-18 11:04:00