Will Coleda wrote:
On Sun, Jul 19, 2009 at 10:50 PM, Christoph Otto via
RT wrote:
On Sun Jul 19 16:18:01 2009, jk...@verizon.net wrote:
Would any of the participants in this thread be able to post an update?
Was the TGE refactor ever done?
If not, is it still needed in light of subsequent wor
On Sun, Jul 19, 2009 at 10:50 PM, Christoph Otto via
RT wrote:
> On Sun Jul 19 16:18:01 2009, jk...@verizon.net wrote:
>> Would any of the participants in this thread be able to post an update?
>>
>> Was the TGE refactor ever done?
>>
>> If not, is it still needed in light of subsequent work on the
On Sun Jul 19 18:27:29 2009, tene wrote:
> Parrot still doesn't have a hierarchy of exception types.
> exception;death doesn't exist. This is the same as rt#36261. I
> recommend that both of these tickets be merged into a single TT.
At Tene's suggestion, I am consolidating this ticket with one
On Sun Jul 19 18:22:00 2009, tene wrote:
> This still hasn't been done. I've been thinking about this again
> recently, and I'll try to move it higher in my TODO list. I have a lot
> of exceptions cleanups that I still need to document and/or do.
At Tene's suggestion, I am consolidating this ti
On Mon Dec 01 11:39:33 2008, pmichaud wrote:
>
> ... how exactly does one use C, C,
> and the other exception types from PIR? I see them mentioned throughout
> pdd23, but I've never actually seen an example of how these constants
> (are they constants?) might appear in actual code, whether it's P
Although I cannot be sure that the issues which were cited in the
original post to this RT have been cleared up, I note that there has
been no follow-up discussion in eight months.
So I'm going to resolve this ticket and encourage any new LANG-related
failures to be reported in new tickets in our
This ticket has been moved into the Trac system at
https://trac.parrot.org/parrot/ticket/857.
Please continue the discussion there. Thank you very much.
kid51
There's been a lot of water under the bridge since this test failure
report was originally filed. So we would undoubtedly need new reports
to go forward.
I'm going to close this ticket and encourage people with access to
NexentaOS (GNU/OpenSolaris) to configure and build Parrot from HEAD and
to f
This ticket addressed a variety of issues why may or may not still be
apropos. However, I suspect that the specific approach to
install-related problems suggested in the ticket will be superseded by
the work done on such issues in the last month.
Would it be possible to review this ticket and rec
On Sun, Jul 19, 2009 at 3:09 PM, Patrick R. Michaud wrote:
> On Sat, Jul 18, 2009 at 01:47:51AM -0700,
> christian.aperg...@lidil.univ-mrs.fr (via RT) wrote:
>> I am afraid to see that the Rakudo site is used by plenty of spammers to
>> provide their messages.
>>
>> You can find several comments i
On Sat, Jul 18, 2009 at 01:47:51AM -0700, christian.aperg...@lidil.univ-mrs.fr
(via RT) wrote:
> I am afraid to see that the Rakudo site is used by plenty of spammers to
> provide their messages.
>
> You can find several comments in languages that are ununderstandable for
> us (arabic, turkish)
This ticket has been moved into the Trac system:
https://trac.parrot.org/parrot/ticket/854. Please continue the
discussion there.
Thank you very much.
kid51
On Sat, 2009-07-18 at 21:22 -0400, James Cloos wrote:
> lwall> + enum TrigBase is export ;
>
> Is Circles of much value?
>
> I can see Semicircles, since that would make the range (-1,1] or [-1,1).
> But a range of [0,1) or (0,1] seems *much* less useful.
>
> Or am I missing an obvious use case?
This is an automatically generated mail to inform you that tests are now
available in b/t/spec/S05-metasyntax/regex.t
lwall> + enum TrigBase is export ;
Is Circles of much value?
I can see Semicircles, since that would make the range (-1,1] or [-1,1).
But a range of [0,1) or (0,1] seems *much* less useful.
Or am I missing an obvious use case?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
15 matches
Mail list logo
