The document "Priority Queues for Common Lisp" has been submitted by Marco Antoniotti and has been accepted as CDR document 13. According to the CDR process, this document is now in its initial stage and will be finalized on March 31, 2013, unless withdrawn by the author beforehand. See http://cdr.eurolisp.org/document/13/ for the details of this document.
--
Pascal Costanza
_______________________________________________
cdr-announce mailing list
cdr-announce(a)common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce
The document "Generic extendable heaps for Common Lisp" (CDR 12) has been withdrawn. According to the CDR process, we now only list the title of the document and indicate the withdrawn status for the records.
--
Pascal Costanza
_______________________________________________
cdr-announce mailing list
cdr-announce(a)common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce
Dear Lispers,
We're glad to announce the USOCKET 0.6.0 release.
Changes in this release:
* New feature: SOCKET-OPTION and (setf SOCKET-OPTION) for seting and geting various socket options.
* New feature: SOCKET-SEND now support an CCL-like OFFSET keyword for sending only parts of the whole buffer.
* New feature: [ECL] Added support for ECL DFFI mode on Windows. (no need for C compilers now)
* Bugfix: [ECL] ECL now list sb-bsd-sockets as a dependency but relies on REQUIRE. (patched by Juanjo)
* Bugfix: [ABCL] Make USOCKET compile warning-free on ABCL again: MAKE-IMMEDIATE-OBJECT was deprecated a while ago in favor of 2 predefined constants.
* Bugfix: [LispWorks] remove redundant call to hcl:flag-special-free-action. (reported by Kamil Shakirov)
* Bugfix: [CLISP] improved HANDLE-CONDITION for more CLISP environments.
For the new API, SOCKET-OPTION, initially we support following options:
* RECEIVE-TIMEOUT (SO_RCVTIMEO)
* REUSE-ADDRESS (SO_REUSEADDR), for TCP server
* BROADCAST (SO_BROADCAST), for UDP client
For usage of SOCKET-OPTION and (SETF SOCKET-OPTION), please directly take a look at "option.lisp" from USOCKET source code. We'll add documentation later.
(Unfortunately, not all CL platforms were full supported at current time, but we'll fix the missing part soon)
As usual, if you want to download this release, please check
http://common-lisp.net/project/usocket/releases/
or just wait for next Quicklisp monthly dist updates.
The API documentation page was here (but I haven't updated it for SOCKET-OPTION yet ...):
http://common-lisp.net/project/usocket/api-docs.shtml
As usual, any feedback - bugs or hugs - is greatly appreciated.
P. S. Something currently still in progress:
* New feature: CLISP support some advanced TCP features which CLISP's SOCKET interface not provide
* New feature: Macintosh Common Lisp (MCL) support Datagram sockets (UDP), based on OpenTransport.
* New feature: SOCKET-SHUTDOWN for TCP and UDP sockets.
Regards,
Chun Tian (binghe)
USOCKET Team
_______________________________________________
usocket-announce mailing list
usocket-announce(a)common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/usocket-announce
Hi all,
I'm pleased to announce the last CLFSWM 1212 version.
There is minor changes since the last 1209 version but some ugly bugs
has been fixed.
Here is a small resume of the git log information:
* load.lisp do no run CLFSWM by default. It build an executable lisp
image and can download CLX and ASDF if needed (this will help (I
hope) lisp newbies).
* The ./configure as been replaced by a simple Makefile which ease the
load of load.lisp (it search for available lisp implementations).
* New .desktop files to ease the login manager integration.
* Some bug fixes on multi heads monitors to add or remove monitors on
the fly. Non xinerama configuration are correctly handled.
* Add support for numeric keypad with numlock on.
* Key bindings for main and second mode are shown in menu entry.
* I've added an blank-window-mode in contrib/. This way, we can hide
part of the screen with blank window. I'm pretty sure nobody except
me will use it but it's very useful in school class to hide some
part of the screen on interactive presentation with a video
projector.
I think this version is pretty clean. So I'll made more announcement
about it ((fr.)comp.land.lisp and french slashdot equivalent). I don't
know where I can make english announcement/presentation (slashdot
doesn't seem the place). So if you like it, feel free to share your
feeling about CLFSWM. This way, maybe it will show up again on Wikipedia :-)
As always any feedback is very welcome.
Have fun,
Philippe
_______________________________________________
clfswm-announce mailing list
clfswm-announce(a)common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clfswm-announce
The document "Generic extendable heaps for Common Lisp" has been submitted by Ingvar Mattsson and has been accepted as CDR document 12. According to the CDR process, this document is now in its initial stage and will be finalized on January 1, 2012, unless withdrawn by the author beforehand. See http://cdr.eurolisp.org/document/12/ for the details of this document.
--
Pascal Costanza
_______________________________________________
cdr-announce mailing list
cdr-announce(a)common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce
The document "Standard output streams default behavior in terminal sessions" has been finalized. According to the CDR process, this document is now in its final stage and cannot be changed anymore. See http://cdr.eurolisp.org/document/11/ for the details of this document.
--
Pascal Costanza
_______________________________________________
cdr-announce mailing list
cdr-announce(a)common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce
The document "Functions COMPILED-FILE-P and ABI-VERSION" has been finalized. According to the CDR process, this document is now in its final stage and cannot be changed anymore. See http://cdr.eurolisp.org/document/10/index.html for the details of this document.
--
Pascal Costanza
_______________________________________________
cdr-announce mailing list
cdr-announce(a)common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce
Hi Steve,
Thanks a lot indeed for your interest in CDR.
The rationale for CDR is explained at http://cdr.eurolisp.org/ on the opening page. You should find all answers to the question you posted on that page.
But let me stress a few points directly related to your questions:
- It is certainly possible to discuss a CDR after it has been finalized.
- More specifically, it's also certainly possible to refine a CDR after it has been finalized. However, the particular CDR (with a specific CDR number) cannot be changed anymore. If you want to refine a finalized CDR, you have to submit a new one, which will then receive a new CDR number. New CDRs can claim to updates to existing CDRs. (For example, it is already the case that CDR 4 is a refinement of CDR 0, and the whole CDR process is currently based on CDR 4 rather than CDR 0.)
- Whether a particular CDR is eventually accepted by the community or not is in the hands of the community, not in the hands of the CDR editors. CDR is only a repository for documents, not a body that can enforce or endorse standards. This was an intentional design decision, to avoid the need for CDR editors to judge the contents of CDR documents (which they don't), and to avoid legal implications.
- There are three mailing lists associated with CDR: cdr-announce is for announcements, cdr-devel is for discussions about the CDR repository and process itself, and cdr-discuss is for discussions about specific CDRs. If you would like to continue a discussion about CDR itself, please do so on cdr-devel. Didier (the author of CDR 11) seems to be willing to discuss CDR 11 on cdr-discuss, so if you are interested in that, please discuss it there. (Authors are encouraged, but not required to discuss documents. Again, CDR is intentionally a light-weight process: Any requirements imposed on authors would need to be checked, and CDR is designed to require as few checks as possible. That's why documents don't even need to be discussed, because it would be hard to judge what would qualify as a "sufficient" amount of discussion. We believe that members of the community are mature enough to decide for themselves what constitutes a "good" CDR or not.)
Again, thanks a lot for your interest. I hope this clarifies your questions. Please feel free to comment or discuss this further, if you think there is room for improvement.
Best,
Pascal
P.S.: I personally believe that Duane Rettig's proposal for environment access would be an excellent candidate for a CDR. Franz Inc. probably has more extensions that would be good contributions. Please let us know if we can help with submitting CDR documents, in case you are interested.
On 8 Jun 2012, at 06:49, Steve Haflich wrote:
> Pascal et al.
>
> I'm confused, or perhaps only ignorant, about the process underlying the
> CDR repository. Once a CDR becomes final after a very short time, there
> seems to be no forum or machinery to discuss or refine it. While I find
> myself sympathetic to at least some of the stated problems, none of the
> stated solutions are fully acceptable -- there are glitches in the
> specifications, or important situations missed, or incompatibilities
> between proposed changes and the official sanctity of the CL package.
>
> Is there some forum for further discussion of "final" CDRs? Otherwise
> the CDRs seem a rather profitless exercise.
>
> _______________________________________________
> cdr-announce mailing list
> cdr-announce(a)common-lisp.net
> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce
--
Pascal Costanza
The views expressed in this email are my own, and not those of my employer.
_______________________________________________
cdr-announce mailing list
cdr-announce(a)common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce