Need Win32 Tinder suggestions
Dan Sugalski
Pro gadget with Visual Studio .NET. I'm going to install cygwin as well.
I'll be setting up tinderboxes for it but, honestly, I don't do windows
programming, so I'm not particularly sure what'd be useful. I'm going to
try and get JIT and non-JIT tinders for both vanilla VS and cygwin builds,
but I'd be more than happy if someone with some actual windows experience
would throw in some suggestions on what and how to set things up for the
maximum utility.
Dan
Dan Sugalski
> Based on current customers I would guess the following in priority:
>
> VC/C++ (latest non-.NET version, most people I know are still building
> their stuff with Pre-.NET versions)
> Visual Studio .NET
> Cygwin
> Borland C++ Builder
I don't have VC/C++ or Borland -- if someone gets me copies I'll install
them and make 'em build as well.
> Hey where is my free P6E copy? :P
D'oh! Sitting on my bureau waiting to get packaged up and mailed. You sent
me your address, right?
Dan
Dan Sugalski
> Eep, I was too busy poking fun at Dan about the book I forgot to say:
>
> 1) I do not represent IBM nor IBM's preferences for development
> environment, I was just guessing.
> You are welcome to add IBM Visual Age stuff in there, let me know if
> you need a license. :)
And media! (Or a download location) I'd be thrilled to have it up and
running. I should probably try and find a license for Intel's compiler
too. (I think the 80G drive on this thing may end up being too small...)
> 2) The P6E book was well done, I did finally get a look at it at Barnes
> and Noble. Good job Dan/Leo.
And it's your job, if you choose to accept it, to help make it horribly
out-of-date. :)
Dan
Nicholas Clark
> And it's your job, if you choose to accept it, to help make it horribly
> out-of-date. :)
Are there going to be (booby) prizes for the people who make the most
paragraphs obsolete? Is anyone counting?
(Who do I score the U-turn on page 93 to?)
Nicholas Clark
Dan Sugalski
> I do have an older version of Borland that I can mail you, but I think it
> is at least 2 releases old
> As for Microsoft I can't help with a license, but I can probably get us
> one for IBM Visual Age.
I may be able to scare up media and license from MS for VS/C++. They're
the folks that got us the VS/.NET kit.
> I assume you have a lot of disk space?
With 80 gig I thought I did, but I'm not so sure at this point... :)
> Doesn't Borland have some sort of free download version that is
> non-commercial usable? I'll check.
I honestly don't know. It's been a few years since I used Windows, and at
that point it was mostly as an X client, Eudora host, DVD player, and
cygwin setup. I don't know about all these fancy "gooey" tools everyone's
using... :-P
Dan
Dan Sugalski
> On Thu, Sep 11, 2003 at 03:16:15PM -0400, Dan Sugalski wrote:
> > And it's your job, if you choose to accept it, to help make it horribly
> > out-of-date. :)
>
> Are there going to be (booby) prizes for the people who make the most
> paragraphs obsolete? Is anyone counting?
Heh. We ought to do that. Winner gets a mention in the forward of the next
version. Dunno if we should send on a signed copy, or a hand corrected
version of the old copy.
> (Who do I score the U-turn on page 93 to?)
Don't have it handy. Which U-turn is that?
Dan
Brent Dax
# > (Who do I score the U-turn on page 93 to?)
#
# Don't have it handy. Which U-turn is that?
Presumably, "Coroutines can be implemented in terms of continuations if
need be, but that requires using a full continuation-passing function
call system, something we chose not to do."
--Brent Dax <br...@brentdax.com>
Perl and Parrot hacker
"Yeah, and my underwear is flame-retardant--that doesn't mean I'm gonna
set myself on fire to prove it."
Dan Sugalski
> Dan Sugalski:
> # > (Who do I score the U-turn on page 93 to?)
> #
> # Don't have it handy. Which U-turn is that?
>
> Presumably, "Coroutines can be implemented in terms of continuations if
> need be, but that requires using a full continuation-passing function
> call system, something we chose not to do."
Ah. That one's the collective fault of the denizens of the Little
Languages mailing list and the MIT Lisp and/or Scheme folks.
Dan
Brent Dax
# Ah. That one's the collective fault of the denizens of the Little
# Languages mailing list and the MIT Lisp and/or Scheme folks.
Oh, and in case it wasn't abundantly clear before, I already picked up a
copy--a month or so ago, while I was on vacation and needed something to
read during long drives. It was good, but not long enough to last from
Virginia to Philadelphia. ;^)
Dan Sugalski
> Dan Sugalski:
> # Ah. That one's the collective fault of the denizens of the Little
> # Languages mailing list and the MIT Lisp and/or Scheme folks.
>
> Oh, and in case it wasn't abundantly clear before, I already picked up a
> copy--a month or so ago, while I was on vacation and needed something to
> read during long drives. It was good, but not long enough to last from
> Virginia to Philadelphia. ;^)
You were supposed to take the rest of the time and sketch out a grammar
for perl 6 regular expressions. Did we leave that bit out of the end of
the book? (Damn, one more erratta to add! :)
Dan
Nicholas Clark
> Dan Sugalski:
> # > (Who do I score the U-turn on page 93 to?)
> #
> # Don't have it handy. Which U-turn is that?
>
> Presumably, "Coroutines can be implemented in terms of continuations if
> need be, but that requires using a full continuation-passing function
> call system, something we chose not to do."
That would be the one:
http://www.ccl4.org/~nick/P/p6ee++.jpeg
(thanks to my housemate hoggy for taking the picture)
I think that a fully hand corrected first edition would make quite an
interesting prize.
Nicholas Clark
Matt
windows box. However, I have a quick question first, and didn't want
to bug people too much about it with a new thread.
When I do (n)make test and run all the tests, and some of them fail,
should they ALWAYS be reported? I'd assume so, but just want to know
proper etiquette on here.
t/pmc/io............NOK 3# Failed test (t/pmc/io.t at line 38)
# got: 'fdopen failed
# '
# expected: 'ok
# '
t/pmc/io............NOK 4# Failed test (t/pmc/io.t at line 52)
# got: 'fdopen failed
# '
# expected: 'ok
# '
That's what I got.