> io/io_win32.c
> io_win32.c
> io/io_win32.c(212) : error C2371: 'PIO_win32_flush' : redefinition;
> different basic types
> io/io_win32.c(49) : see declaration of 'PIO_win32_flush'
> NMAKE : fatal error U1077: 'C:\Perl\bin\perl.exe' : return code '0x2'
> Stop.
I succeeded in fixing it(io_
On Tue, Sep 02, 2003 at 11:17:00PM +0200, Paul Johnson wrote:
> On Tue, Sep 02, 2003 at 01:43:06PM +0200, Paul Johnson wrote:
>
> > I've finally found no compelling reasons not to release Devel::Cover
> > 0.21.
>
> And hot on its heels comes 0.22.
You wait for ages, and then three come along at
(I am way, way behind on reading this mailing list.)
Assuming I understand your scheme properly, it seems incorrect to me.
An object must be finalized during the first 'sweep 0' after it is no
longer reachable from the root set. (And no object may be finalized
while it is still reachable, but y
Steve Fink writes:
> (I am way, way behind on reading this mailing list.)
>
> Assuming I understand your scheme properly, it seems incorrect to me.
>
> An object must be finalized during the first 'sweep 0' after it is no
> longer reachable from the root set. (And no object may be finalized
> w
Jonathan Worthington wrote:
Hi,
I want to include pdump and disassemble
$(MAKE) world
(since now ;-)
leo
Luke Palmer <[EMAIL PROTECTED]> wrote:
> In any case, seeing that depth first case (see the footnote) has given
> me even more hope that I won't be agonizing over scope exit.
Can you summarize your scheme again please WRT this and other
enhancements. I'm somewhat lost in all the improvements that
On Thursday, September 4, 2003, at 10:56 , Luke Palmer wrote:
Is there a problem with providing a mechanism which would suspend all
threads except for the "current" one, as to ensure that the serialize
operates, er, serially. Could it be implemented with a top-priority
event post that acquires
On Thu, 4 Sep 2003 [EMAIL PROTECTED] wrote:
> On Mon, 1 Sep 2003, Michael G Schwern wrote:
> > You also must worry about volumes.
[my long explanation snipped]
Sorry, wrong list; this is a standard-module issue, not an implementation
issue or even a core-language issue.
-Martin
me wrote:
> libparrot_s.lib(io_buf.obj) : error LNK2001: unresolved external symbol
> _PIO_win
> 32_getblksize
> libparrot_s.lib(io_buf.obj) : error LNK2001: unresolved external symbol
> _PIO_win
> 32_isatty
> parrot.exe : fatal error LNK1120: 2 unresolved externals
> NMAKE : fatal error U1077: 'li
Daniel Grunblatt wrote:
On Friday 05 September 2003 12:34, Steve Fink wrote:
In my own coding, I follow the rule of "leave it out if the type tells
you everything you need to know about the purpose." But that's a
subjective decision, and therefore dangerous to put in a coding style
guide.
I am working on adding support for additional chartypes to Parrot, plus
the capability for run-time registration of same. To this end, I would like to:
1) Add CHARTYPE* as a parameter to the _is_digit/_get_digit functions
2) Create a new struct chartype_digit_map_t to contain mappings from code va
Leopold Toetsch writes:
> Luke Palmer <[EMAIL PROTECTED]> wrote:
>
> > In any case, seeing that depth first case (see the footnote) has given
> > me even more hope that I won't be agonizing over scope exit.
>
> Can you summarize your scheme again please WRT this and other
> enhancements. I'm some
On Fri, 5 Sep 2003, Peter Gibbs wrote:
> I am working on adding support for additional chartypes to Parrot, plus
> the capability for run-time registration of same. To this end, I would like to:
>
> 1) Add CHARTYPE* as a parameter to the _is_digit/_get_digit functions
> 2) Create a new struct cha
On Fri, 5 Sep 2003, Dan Sugalski wrote:
> Go for it. There is the possibility that identifying a digit is more
> involved than we might otherwise want for some chartypes, however--the
Yeah - I am hoping to handle the simpler cases generically, so that we only
need to write specific code for the
On Thu, 4 Sep 2003 09:02:18 -0400 (EDT), Dan Sugalski wrote:
> On Wed, 3 Sep 2003, Gordon Henriksen wrote:
> > A seen hash is also threadsafe, can be interrupted by DoD, and is safe
> > for recursion. (By "threadsafe," I mean that unchanged data structures
> > can be safely serialized from multiple
On Fri, 5 Sep 2003, Peter Gibbs wrote:
> On Fri, 5 Sep 2003, Dan Sugalski wrote:
>
> > Go for it. There is the possibility that identifying a digit is more
> > involved than we might otherwise want for some chartypes, however--the
>
> Yeah - I am hoping to handle the simpler cases generically,
On Fri, 5 Sep 2003, Peter Haworth wrote:
> On Thu, 4 Sep 2003 09:02:18 -0400 (EDT), Dan Sugalski wrote:
> > On Wed, 3 Sep 2003, Gordon Henriksen wrote:
> > > A seen hash is also threadsafe, can be interrupted by DoD, and is safe
> > > for recursion. (By "threadsafe," I mean that unchanged data str
Peter Gibbs <[EMAIL PROTECTED]> wrote:
> +if (!chartype_array)
>chartype_init();
> +if (!encoding_array)
>encoding_init();
T think, both should be done at interpreter startup, called from
string.c:string_init().
leo
Leopold Toetsch wrote:
> Peter Gibbs <[EMAIL PROTECTED]> wrote:
> > +if (!chartype_array)
> >chartype_init();
> > +if (!encoding_array)
> >encoding_init();
>
> T think, both should be done at interpreter startup, called from
> string.c:string_init().
>
> leo
I
Luke Palmer <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch writes:
>>
>> Can you summarize your scheme again please WRT this and other
>> enhancements. I'm somewhat lost in all the improvements that were
>> proposed since your original.
> Alright, here's a patch that implements it.
Wow.
Some remar
On Thu, Sep 04, 2003 at 09:05:54PM -0600, Luke Palmer wrote:
>
> Oops. Well, I said I, didn't I? Doesn't mutt know what I
> mean!? %-)
It's not that smart :-)
But it does spot the references headers and thread messages that are actually
replies to existing messages, even when the subject and
Tim Bunce wrote:
On Sun, Aug 24, 2003 at 10:48:02AM -0700, Steve Fink wrote:
I guess you could think of the lifecycle of an individual object as
being controlled by a few significant life events:
1. birth
2. the last reference disappearing
3. finalization
4. destruction
That's a nice idea,
Hi,
The current implementation of fdopen op in PIO is buggy. The tests
fail currently on every system except unix. This is because the test
are based on the assumption of 1 being stdout on every system.
Furhtermore the standard handles get autoclosed at exit. This has in
the past lead to problems
Nicholas Clark wrote:
On Tue, Sep 02, 2003 at 06:39:23AM +0300, Vladimir Lipskiy wrote:
D. Function parametres in declarations.
At the monent, pdd7 says that we mustn't omit them in declarations.
I propose to omit them. The advantage is: We wouldn't run the risk to
having a keyword of C++ as
On Friday 05 September 2003 12:34, Steve Fink wrote:
> Nicholas Clark wrote:
> >On Tue, Sep 02, 2003 at 06:39:23AM +0300, Vladimir Lipskiy wrote:
> >>D. Function parametres in declarations.
> >>
> >>At the monent, pdd7 says that we mustn't omit them in declarations.
> >>I propose to omit them. The
Leopold Toetsch wrote:
> Jonathan Worthington wrote:
>
> > Hi,
> >
> > I want to include pdump and disassemble
>
>
> $(MAKE) world
>
> (since now ;-)
Thanks! That's really great. :-)
Or would be... Just went to rebuild it on Win32 with latest CVS checkout:-
io/io_win32.c
io_win32.c
io/io_win32
> --- Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> > Amir Karger <[EMAIL PROTECTED]> wrote:
[fixes]
> > I'll put in these fixes.
Thanks!
> >
> > > The bad news is that when I then try to parrot it, Windows throws
> > > me an error window saying parrot died. I don't know why.
> >
> > linux SIG
27 matches
Mail list logo
