release update

release update

[Andy Wingo]

Hey Guilers,

I didn't push anything specific regarding a freeze, but in practice
since we're so few, we've been great at just putting in release-worthy
fixes :)

I would say that we are definitely on track for a 1.9 on the 19th. I
have a list of things to add to the NEWS, which I'm appending to this
mail just to give some scope -- the list only goes back to September of
last year, when it really needs to go back to May or so when I started
work on the VM, but it's close to complete WRT what I need to add.

Please add on any missing points. Note that the 1.9 release notes will
become the 2.0 release notes, I think; over the next few months we will
be editing them, adding and removing things, so that readers for the 2.0
release will understand what it is we've been up to over the last few
years.

One question is that I've been calling this thing 1.9.1 under the
assumption that we made a 1.9.0; but that does not seem to be the case.
Should this one be 1.9.0 or 1.9.1?

OK, enough rambling. I have a plane flight tomorrow in which to write
proper NEWS entries, after which hopefully all will be set for a release
on Friday.

Cheers,

Andy

raw NEWS notes:

stack limits -- rlimit and default limit

fix false-if-exception

automatic compilation -- note mtime implications

GUILE_LOAD_COMPILED_PATH, %load-compiled-path, %load-compiled-extensions

the ~/.guile-ccache dir

libdir installs for compiled code

scm_primitive_load_path additional arg: exception_on_error

scm_stat exception_on_error optional arg

ccachedir to build-info ?

#', #`, #,, #,@ -- and note the difference

#;

tail calls and stack narrowing

source location tracking in psyntax

macros before uses of macros

no more currying

modules do have names -- even gensymmed named

different syntax exception strings (and sometimes keys?)

values truncates

values in the some cases requires 1 value

interactions between hygienic macros and defmacros

first-class macro values

psyntax propagates original variable names -- into compiled code only,
though

the extended macro types -- make-syncase-macro,
make-extended-syncase-macro, macro-type, syncase-macro-type,
syncase-macro-binding

removed sc-expand3

remove (void)

(ice-9 syncase) deprecated -- and along with that, andmap, void, ...

syntax-dispatch -> $sc-dispatch

syntax-object->datum -> syntax->datum, etc

no more syntax-error; but syntax-violation, yes.

no more sc-macro

fix module-bound? if the local variable was not bound, b
    * module/ice-9/boot-9.scm (module-bound?): module-bound? was returning
      true if (not (variable-bound? (module-local-variable m v))), but
      (variable-bound? (module-variable m v)). Fix to cut out on the first
      variable it finds. This bug has been there for a while now.

BUGS: autocompilation when it shouldn't: elisp.

change in the meaning of module transformers? was there really?

BUG: disabled macroexpansion of emacs lisp code

defmacros may now have docstrings

eval-case and eval-when

definitions in expression context

unquoting values into defmacro expansions

allow docstrings with internal definitions with syntax-case etc

eval-when for functions used by macros

scoping of "keywords" -- important?

(ice-9 syncase) deprecated

can now redefine keywords to normal values

new defns: bound-identifier=? free-identifier=? generate-temporaries
identifier?

%pre-modules-transformer

remove macroexpand, macroexpand-1; should add macroexpand back in tho

FIXME bytevectors.

FIXME unistring.

more robust threading support.

syncase knows about @/@@

macros and hygiene and modules

eval-closure-module? what?

procedure-module / scm_procedure_module

guile-config info sitedir change -- 922d369

guile-config and pkg-config

(system xref), procedure-callers, procedure-callees, can work as
variables get redefined

getrlimit and setrlimit wrappers

FIXME: getrlimit crazy namespaces...

add method-formals

BUG? procedure-property 'arity on compiled procedures will be wrong

BUG: SCM_SNAME -> SCM_SUBR_NAME

(ice-9 session):
add-value-help-handler! remove-value-help-handler!
add-name-help-handler! remove-name-help-handler!
export module-commentary
procedure-arguments

procedure->memoizing-macro, procedure->syntax totally superdeprecated?

FIXME: update copyrights

ecmascript support?

new repl...

guile-tools compile, guile-tools disassemble (does that work?)

BUG: stack walks to see number of frames, then fills those frames.
sometimes those numbers differ, warning to console, a test case would be
nice.

FIXME: dance disassembly bug

srfi-18

<method> has formals, body slots; (make-procedure & procedure ?)

FIXME: rewrite while

removed (the-environment)

new function: scm_module_public_interface

BUG: help at guile prompt

new procedure, make-promise

-- 
http://wingolog.org/

Re: release update

[Neil Jerram]

Andy Wingo <wingo@pobox.com> writes:

> Hey Guilers,

Hi Andy!

> I didn't push anything specific regarding a freeze, but in practice
> since we're so few, we've been great at just putting in release-worthy
> fixes :)
>
> I would say that we are definitely on track for a 1.9 on the 19th.

Agreed.

> I have a list of things to add to the NEWS, which I'm appending to
> this mail just to give some scope -- the list only goes back to
> September of last year, when it really needs to go back to May or so
> when I started work on the VM, but it's close to complete WRT what I
> need to add.
>
> Please add on any missing points. Note that the 1.9 release notes will
> become the 2.0 release notes, I think; over the next few months we will
> be editing them, adding and removing things, so that readers for the 2.0
> release will understand what it is we've been up to over the last few
> years.
>
> One question is that I've been calling this thing 1.9.1 under the
> assumption that we made a 1.9.0; but that does not seem to be the case.
> Should this one be 1.9.0 or 1.9.1?

I think either is good.  (The only other factor that occurs to me is a
very silly one, namely that thus far we have got away with being able
to use string<? to compare Guile versions!  If we ever reached 1.9.10
(or 1.8.10, for that matter), that would no longer work.)

> OK, enough rambling. I have a plane flight tomorrow in which to write
> proper NEWS entries, after which hopefully all will be set for a release
> on Friday.

Some notes/queries on a few of your notes...

> no more currying

I thought that was unintentional, and have it on my todo list as a
bug.  Is it actually intentional?

> more robust threading support.

Does this mean SRFI-18?  "more robust" isn't quite right for that,
IMO; I'd say "more sophisticated API" or something.

> srfi-18

Oh, maybe not then :-)

I also made a checklist, here:
http://article.gmane.org/gmane.lisp.guile.devel/7971

My target, though, is to make sure this is all well covered in NEWS by
the time we get to the actual 2.0.  I'm not very concerned about NEWS
being incomplete during the 1.9.x prereleases.

Regards,
        Neil

Re: release update

[Ludovic Courtès]

Andy Wingo <wingo@pobox.com> writes:

> One question is that I've been calling this thing 1.9.1 under the
> assumption that we made a 1.9.0; but that does not seem to be the case.
> Should this one be 1.9.0 or 1.9.1?

I'd say 1.9.0.

> guile-config and pkg-config

We should deprecate the former, BTW, if this hasn't already been done.

> (system xref), procedure-callers, procedure-callees, can work as
> variables get redefined

I think this should be added to the manual as well.

> BUG: SCM_SNAME -> SCM_SUBR_NAME

Ooh, I didn't worry much about it back then.  Should we?

> FIXME: update copyrights

Yes.

(There's "(add-hook 'write-file-hooks 'copyright-update)", which I find
convenient.)

> ecmascript support?

Yes, although it's currently undocumented.

> new function: scm_module_public_interface

Speaking of which, I was thinking at some point about adding a
`public-interface' slot to `module-type', to avoid hash table lookups.
What do you think?

Thanks,
Ludo'.

Re: release update

[Andy Wingo]

On Thu 18 Jun 2009 23:01, ludo@gnu.org (Ludovic Courtès) writes:

>> guile-config and pkg-config
>
> We should deprecate the former, BTW, if this hasn't already been done.

Indeed, though we need to keep it working through 2.0, at least until
new guile.m4 (yet to be ported...) becomes common.

>> (system xref), procedure-callers, procedure-callees, can work as
>> variables get redefined
>
> I think this should be added to the manual as well.

Yes.

>> BUG: SCM_SNAME -> SCM_SUBR_NAME
>
> Ooh, I didn't worry much about it back then.  Should we?

I fixed this one. SNAME was very confusing to me :)

>> FIXME: update copyrights
>
> Yes.
>
> (There's "(add-hook 'write-file-hooks 'copyright-update)", which I find
> convenient.)

Looks like Neil took care of things. I've added this one to my .emacs.

>> ecmascript support?
>
> Yes, although it's currently undocumented.

Indeed, needs fixing.

>> new function: scm_module_public_interface
>
> Speaking of which, I was thinking at some point about adding a
> `public-interface' slot to `module-type', to avoid hash table lookups.
> What do you think?

Yes! %module-public-interface is a terrible hack.

Andy
-- 
http://wingolog.org/

Re: release update

[Neil Jerram]

Andy Wingo <wingo@pobox.com> writes:

>>> FIXME: update copyrights
>>
>> Yes.
>>
>> (There's "(add-hook 'write-file-hooks 'copyright-update)", which I find
>> convenient.)
>
> Looks like Neil took care of things. I've added this one to my .emacs.

I'm afraid not.  I think I updated one or two cases in passing, but I
didn't do a complete job.

Regards,
        Neil