Home     |     .Net Programming    |     cSharp Home    |     Sql Server Home    |     Javascript / Client Side Development     |     Ajax Programming

Ruby on Rails Development     |     Perl Programming     |     C Programming Language     |     C++ Programming     |     IT Jobs

Python Programming Language     |     Laptop Suggestions?    |     TCL Scripting     |     Fortran Programming     |     Scheme Programming Language


 
 
Cervo Technologies
The Right Source to Outsource

MS Dynamics CRM 3.0

Scheme Programming Language

Thanks to the R6RS committee!


I want to thank the R6RS committee for putting in the extraordinary
effort to create the R6RS draft.

Like many people, I have some reservations and concerns about parts of
proposal, and I am excited and pleased by other parts.  But whether
the proposal is ratified or not, and whether anyone implements any
part of it or not, the committee deserves credit for taking the time
and energy to put together the proposal.

I hope others in the community will join me in saying `Thanks!' for
the work regardless of whether they intend to vote for or against
ratification.

Joe Marshall wrote:
> I want to thank the R6RS committee for putting in the extraordinary
> effort to create the R6RS draft.

> Like many people, I have some reservations and concerns about parts of
> proposal, and I am excited and pleased by other parts.  But whether
> the proposal is ratified or not, and whether anyone implements any
> part of it or not, the committee deserves credit for taking the time
> and energy to put together the proposal.

> I hope others in the community will join me in saying `Thanks!' for
> the work regardless of whether they intend to vote for or against
> ratification.

+1 :-)

If I may add one thing.  Please wait and read the final draft before
making up your mind and don't jump to conclusions based on earlier
drafts.  Who knows, you might have liked one draft but hate the
final version (or the other way around).

Aziz,,,

On May 23, 12:37 pm, Joe Marshall <eval.ap@gmail.com> wrote:

> I want to thank the R6RS committee for putting in the extraordinary
> effort to create the R6RS draft.

> Like many people, I have some reservations and concerns about parts of
> proposal, and I am excited and pleased by other parts.  But whether
> the proposal is ratified or not, and whether anyone implements any
> part of it or not, the committee deserves credit for taking the time
> and energy to put together the proposal.

> I hope others in the community will join me in saying `Thanks!' for
> the work regardless of whether they intend to vote for or against
> ratification.

+2 :-)

I totally agree with Joe's statement. Thanks to the R6RS committee for
their wonderful work and dedication to Scheme.

Guillaume Cartier

Guillaume Cartier wrote:
> I totally agree with Joe's statement. Thanks to the R6RS committee for
> their wonderful work and dedication to Scheme.

Thank you for this, Guillaume, and also for your own
wonderful work on JazzScheme.  Very impressive,
and we applaud your efforts to make it available in
a more portable form.

Will

On 5 24 ,   1 37 , Joe Marshall <eval.ap@gmail.com> wrote:

> I want to thank the R6RS committee for putting in the extraordinary
> effort to create the R6RS draft.

> Like many people, I have some reservations and concerns about parts of
> proposal, and I am excited and pleased by other parts.  But whether
> the proposal is ratified or not, and whether anyone implements any
> part of it or not, the committee deserves credit for taking the time
> and energy to put together the proposal.

> I hope others in the community will join me in saying `Thanks!' for
> the work regardless of whether they intend to vote for or against
> ratification.

+1 as an ordinary user.
On May 23, 6:37 pm, Joe Marshall <eval.ap@gmail.com> wrote:

> I want to thank the R6RS committee for putting in the extraordinary
> effort to create the R6RS draft.

> Like many people, I have some reservations and concerns about parts of
> proposal, and I am excited and pleased by other parts.  But whether
> the proposal is ratified or not, and whether anyone implements any
> part of it or not, the committee deserves credit for taking the time
> and energy to put together the proposal.

> I hope others in the community will join me in saying `Thanks!' for
> the work regardless of whether they intend to vote for or against
> ratification.

Yeah!

I'd also like to thank the R6RS comittee for the effort and work
that went into the draft. Endless planning, discussion and
confrontations between comittee members must surely
be rather exhausting. So I'd like to say:

Thanks, pals!

The result is a disastrous failure, but, boy, you worked
pretty hard on it.

cheers,
felix

Joe Marshall skrev:

> I want to thank the R6RS committee for putting in the extraordinary
> effort to create the R6RS draft.

> Like many people, I have some reservations and concerns about parts of
> proposal, and I am excited and pleased by other parts.  But whether
> the proposal is ratified or not, and whether anyone implements any
> part of it or not, the committee deserves credit for taking the time
> and energy to put together the proposal.

> I hope others in the community will join me in saying `Thanks!' for
> the work regardless of whether they intend to vote for or against
> ratification.

Well said.

--
Jens Axel Sgaard

Joe Marshall writes:
> I want to thank the R6RS committee for putting in the extraordinary
> effort to create the R6RS draft.

Me too.
Not to be too corny, but I'd like to ignore both the steering
committee and editors for a moment and thank everyone else who
has participated.

Commentators have been doing a good job at everything from
finding small typos to finding definite mistakes to raising
larger "philosophical" objections.  The formal comments have
displayed a lot of care and competence.  Very divergent points
of view have been shared in the discussions, with some degree
of success.  Technical knowledge, such as of implementation
techniques, has been shared.  The editors have been
consistently addressed in challenging yet respectful ways,
with little or no obsequiousness.  Collegiality has prevailed
but not at the cost of suppressing individual style and
personality.

It says something remarkable about the world of Schemers that
such an ad hoc assembly of participants has held to such high
standards.  I think that anyone objectively studying "open
source methodology" who looks at the discussion from a
well-informed perspective will have to marvel, at least a
little bit, and wonder "How'd they do that?"

-t

Add to del.icio.us | Digg this | Stumble it | Powered by Megasolutions Inc