Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

The Perl 6 Essentials book

3 views
Skip to first unread message

Dan Sugalski

unread,
May 26, 2003, 4:06:56 PM5/26/03
to perl6-i...@perl.org
I promised a rundown on what's going on with this book so folks would
know what, why, how, and all that sort of stuff.

The short story is that back in the fall sometime, Allison Randal
pitched a Perl 6 book at O'Reilly. While perl 6 isn't done, and a lot
of information is available online, many people like books, and Ora
felt that folks would but the thing. Which is fine, and we'll see how
that goes.

Allison tagged me to write the parrot architecture chapter, and when
she decided that some actual real assembly was in order (since we do,
after all, have a working VM.... :) the logical guy to tag was Leo,
so she did.

Now, this book is on a tight schedule and, as such, went through a
small tech edit phase. The more people you have the longer it takes,
and this was moving reasonably quickly. (OTOH, the folks doing tech
edit were competent without being in the loop, so the commentary was
quite useful) Allison handled that end of things, as it is her book,
and the fact that nobody on-list got tagged was really just an
oversight by a few really over-worked folks, and for that I'm quite
sorry.

Anyway, here's the upshot. Assuming I'm involved, when it comes time
to do a 2nd edition, I *will* make sure it gets announced here. I
can't guarantee how many technical readers there'll be, as that's a
publisher decision, but we'll try to make sure at least one person
from the list reads the proofs. (Having internal and external readers
is good)

I'll also try and make sure that the folks with CVS access, as well
as some long-time contributors, get a comp copy. Now, this is
something I can't *promise*, but I do get some author copies, I can
nudge O'Reilly, and authors can get books at a discount, so I can
likely swing some copies that way as well. (Assuming spousal
approval, of course--I don't want to risk the wrath and all... :)

And again, sorry about not keeping folks up to date. I plead
desperate overwork and a memory that's very much like something that
I can't actually remember at the moment.
--
Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk

Dan Sugalski

unread,
May 26, 2003, 4:11:26 PM5/26/03
to perl6-i...@perl.org
At 4:06 PM -0400 5/26/03, Dan Sugalski wrote:
>And again, sorry about not keeping folks up to date. I plead
>desperate overwork and a memory that's very much like something that
>I can't actually remember at the moment.

D'oh! Damn memory. I should add that I really, *really* thought I'd
mentioned the book to the list.

Clinton A. Pierce

unread,
May 26, 2003, 4:23:41 PM5/26/03
to perl6-i...@perl.org, Dan Sugalski
# New Ticket Created by Clinton Pierce
# Please include the string: {perl #99999}
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt2/Ticket/Display.html?id=99999 >

Dan's DOD is far too aggressive, and sometimes reclaims memory which is
still in use and failing to run the destructor. This behavior is more
noticable just before the summer conferences, and when major documentation
and planning items are due. Symptoms include forgetfulness and
conversations with himself such as the following:

At 04:11 PM 5/26/2003 -0400, Dan Sugalski wrote:
>At 4:06 PM -0400 5/26/03, Dan Sugalski wrote:
>>And again, sorry about not keeping folks up to date. I plead desperate
>>overwork and a memory that's very much like something that I can't
>>actually remember at the moment.
>
>D'oh! Damn memory. I should add that I really, *really* thought I'd
>mentioned the book to the list.

Memory leaks haven't turned up and he hasn't segfaulted yet, so I wouldn't
consider this a severe bug. I don't have the source code handy to submit a
patch; the usual fix for this is beer and relaxation.


Nicholas Clark

unread,
May 26, 2003, 4:59:35 PM5/26/03
to Dan Sugalski, perl6-i...@perl.org
On Mon, May 26, 2003 at 04:06:56PM -0400, Dan Sugalski wrote:

> desperate overwork and a memory that's very much like something that
> I can't actually remember at the moment.

A jumblie's sea-worthy vessel?

http://www.google.com/search?btnI=I'm+Feeling+Lucky&q=jumblies+sea

Nicholas Clark

PS As penance, can we have objects? <ducks>

Brent Dax

unread,
May 26, 2003, 6:20:28 PM5/26/03
to Dan Sugalski, perl6-i...@perl.org
Dan Sugalski:
# I promised a rundown on what's going on with this book so folks would
# know what, why, how, and all that sort of stuff.
#
# The short story is that back in the fall sometime, Allison Randal
# pitched a Perl 6 book at O'Reilly. While perl 6 isn't done, and a lot
# of information is available online, many people like books, and Ora
# felt that folks would but the thing. Which is fine, and we'll see how
# that goes.

Do you have any sort of release date, even a vague or tentative one? I
know it's not usually decided for sure until a few months beforehand,
but do you at least have a season and year?

--Brent Dax <bren...@cpan.org>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)

>How do you "test" this 'God' to "prove" it is who it says it is?
"If you're God, you know exactly what it would take to convince me. Do
that."
--Marc Fleury on alt.atheism


Brent Dax

unread,
May 26, 2003, 7:03:44 PM5/26/03
to Brent Dax, Dan Sugalski, perl6-i...@perl.org
Ugh, for some reason Outlook split this thread in two, and I didn't see
the older half. Sorry.

Dan Sugalski

unread,
May 26, 2003, 7:06:05 PM5/26/03
to Brent Dax, perl6-i...@perl.org
At 3:20 PM -0700 5/26/03, Brent Dax wrote:
>Dan Sugalski:
># I promised a rundown on what's going on with this book so folks would
># know what, why, how, and all that sort of stuff.
>#
># The short story is that back in the fall sometime, Allison Randal
># pitched a Perl 6 book at O'Reilly. While perl 6 isn't done, and a lot
># of information is available online, many people like books, and Ora
># felt that folks would but the thing. Which is fine, and we'll see how
># that goes.
>
>Do you have any sort of release date, even a vague or tentative one? I
>know it's not usually decided for sure until a few months beforehand,
>but do you at least have a season and year?

Whups, more I forgot. I do, in fact, have a release date, more or
less. The book won't be ready by YAPC::NA, which is June 16-18. It
probably (hopefully, we're shooting for it) will be ready by OSCON,
which is July 7-11. Seeing as I got the QC PDFs today and they're due
back next monday, I presume this can happen if nothing goes wrong,
but it's all magic to me after that.

Randal L. Schwartz

unread,
May 28, 2003, 12:31:28 AM5/28/03
to perl6-i...@perl.org, Dan Sugalski
>>>>> "Dan" == Dan Sugalski <d...@sidhe.org> writes:

Dan> Now, this book is on a tight schedule and, as such, went through a
Dan> small tech edit phase. The more people you have the longer it takes,
Dan> and this was moving reasonably quickly. (OTOH, the folks doing tech
Dan> edit were competent without being in the loop, so the commentary was
Dan> quite useful) Allison handled that end of things, as it is her book,
Dan> and the fact that nobody on-list got tagged was really just an
Dan> oversight by a few really over-worked folks, and for that I'm quite
Dan> sorry.

For some variant definition of "nobody on-list" with which I'm
not familiar.

But I think I know what you mean. :)

Just another underobserved tech-editor from said book, :)

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<mer...@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

Dan Sugalski

unread,
May 29, 2003, 8:20:24 AM5/29/03
to Randal L. Schwartz, perl6-i...@perl.org
At 9:31 PM -0700 5/27/03, Randal L. Schwartz wrote:
> >>>>> "Dan" == Dan Sugalski <d...@sidhe.org> writes:
>
>Dan> Now, this book is on a tight schedule and, as such, went through a
>Dan> small tech edit phase. The more people you have the longer it takes,
>Dan> and this was moving reasonably quickly. (OTOH, the folks doing tech
>Dan> edit were competent without being in the loop, so the commentary was
>Dan> quite useful) Allison handled that end of things, as it is her book,
>Dan> and the fact that nobody on-list got tagged was really just an
>Dan> oversight by a few really over-worked folks, and for that I'm quite
>Dan> sorry.
>
>For some variant definition of "nobody on-list" with which I'm
>not familiar.

I keep forgetting you're here. :)

0 new messages