At 12:08 PM 9/19/2001 -0400, John Siracusa wrote:
>On 9/19/01 11:51 AM, Randal L. Schwartz wrote:
> > John> (HFS and HFS+ are indeed case-insensitive though)
> >
> > Which they *could* have fixed from the Unix side in the same way that
> > MachTen did it..., and I wish they would. In MachTen, eac
At 04:49 PM 9/19/2001 +0100, Robin Houston wrote:
>Dan Sugalski wrote:
> > I'd love to have Darwin there, [...]
> >
> > If someone is willing to pitch in the time and effort, I'd be thrilled
> > to add it to the list.
>
>I'm willing.
Keen. I don't suppose you can do Classic Mac too, perchance?
> "John" == John Siracusa <[EMAIL PROTECTED]> writes:
John> HFS+ supports 255 character file names. Yes, the (classic Mac OS) Finder is
John> hiding something from you, as are the rest of the classic Mac OS file access
John> APIs, which are limited to 32 characters and weren't updated when H
On Wed, Sep 19, 2001 at 08:44:34AM -0600, Nathan Torkington wrote:
> > Don't use parrot-nightly; use the snapshots from cvs.perl.org
>
> So parrot-nightly will only be useful when we have many more features
> implemented, and there's a high probability that most features in a
> snapshot will actu
Simon Cozens writes:
> On Wed, Sep 19, 2001 at 01:22:04PM +0200, H. Merijn Brand wrote:
> > Can't open perl script "t/harness": No such file or directory
> > MANIFEST? (using most recent parrot-nightly)
>
> Don't use parrot-nightly; use the snapshots from cvs.perl.org
So parrot-nightly will only
On 9/19/01 10:35 AM, Randal L. Schwartz wrote:
> John> Someone will correct me if I'm wrong, but I don't think Darwin
> John> even installs on file systems that support anything less than
> John> 255 character file names (e.g. HFS).
>
> My HFS+ drive held Darwin for at least a little while, and t
At 01:10 PM 9/19/2001 +0200, H.Merijn Brand wrote:
>(cast)foo = bar; syntax is *not* supported in most non-GNU C compilers:
My sloppiness, I'll fix anything remaining. (It wasn't done out of any
gcc-centrism--I don't even use gcc much. Just never occurred to me that it
wouldn't work...)
At 11:15 AM 9/19/2001 +0200, H.Merijn Brand wrote:
>If the nightly builds start OK, I could add a daily report for
>
> HP-UX 11.00 HPc/gcc 32/64 threading/non-threading
> HP-UX 10.20 HPc 32threading/non-threading
> AIX 4.3.3 vac/gcc 32/64 threading/non-threading
>
> "John" == John Siracusa <[EMAIL PROTECTED]> writes:
John> On 9/18/01 7:26 PM, Randal L. Schwartz wrote:
>> I'd suggest you "Darwin" there to be sure you're thinking about
>> case-insensitive-32-char filenames
John> Someone will correct me if I'm wrong, but I don't think Darwin
John> even i
> And, maybe even more important, not all the world has gcc!
Hear, hear.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
On Wed 19 Sep 2001 13:10, "H.Merijn Brand" <[EMAIL PROTECTED]> wrote:
> And, maybe even more important, not all the world has gcc!
and bytecode.c
l1:/pro/3gl/CPAN/parrot 136 > make test_prog
cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FI
LE_OFFSET_BITS=64 -I..
On Wed 19 Sep 2001 11:15, "H.Merijn Brand" <[EMAIL PROTECTED]> wrote:
> On Tue 18 Sep 2001 20:43, Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > Okay, folks, the following platforms are considered core for the parrot
> > interpreter. That means we need to run on all of them for any release of
> > t
At 07:55 PM 9/18/2001 +0100, Philip Kendall wrote:
>On Tue, Sep 18, 2001 at 02:43:07PM -0400, Dan Sugalski wrote:
> > Okay, folks, the following platforms are considered core for the parrot
> > interpreter. That means we need to run on all of them for any release of
> > the interpreter to be consi
On Tue, Sep 18, 2001 at 02:43:07PM -0400, Dan Sugalski wrote:
>Linux (x86)
>CygWin
>Win32
>Tru64
>OpenVMS (Alpha)
>Solaris (Sparc)
>FreeBSD (x86)
To clarify: we're *not* saying "these are the only platforms we care
about". Parrot *will* run on many, many more platforms
On Tue, Sep 18, 2001 at 02:43:07PM -0400, Dan Sugalski wrote:
> Okay, folks, the following platforms are considered core for the parrot
> interpreter. That means we need to run on all of them for any release of
> the interpreter to be considerd OK. They are:
[...]
> Solaris (Sparc)
32 bit
Okay, folks, the following platforms are considered core for the parrot
interpreter. That means we need to run on all of them for any release of
the interpreter to be considerd OK. They are:
Linux (x86)
CygWin
Win32
Tru64
OpenVMS (Alpha)
Solaris (Sparc)
FreeBSD (x86)
16 matches
Mail list logo
