All,
As I've continued to develop my Perl-implemented and integratable
RDBMS, a number of aspects have inspired thought for posible
improvements for the Perl 6 language design.
For context, the query and command language of my RDBMS intentionally
overlaps with Perl 6 as much as reasonable;
From: Bob Rogers [EMAIL PROTECTED]
Date: Sun, 12 Nov 2006 21:56:04 -0500
The attached patch adds a docs/pdds/pddXX_dynbind.pod file . . .
Ahem, this patch should have been called dynbind-deep-vars-2.patch
instead of dynbind-shallow-vars-2.patch. I hope this is the only
place I have
On Sat, 11 Nov 2006 16:34:55 -0800, Chip Salzenberg (via RT) wrote
because the Perl sprintf test suite seems to think that the right value
for sprintf('%e',1) is 1e+00, but Win32 seems to return 1e+000 (note
the extra digit in the exponent). Is this true? If so, is it a bug? In
any case,
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Nov 13 14:15:01 2006 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40861]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40861
The t/codingstd/fixme.t test only looks in C-language files for
FIXME|TODO|XXX
To successfully close this ticket, someone needs to write an automated
test (and make it pass!) for the interactive tclsh that checks the
various error handling that was already present (but is now broken),
all tied to the ability to recognize when a command was not done (that
is, unclosed {,
HaloO,
Darren Duncan wrote:
For the record, my preference is to have the generics be the shortest,
[==,!==,=,,,=,=], and use [+,~] prefixes for Num or Str casting
versions. And lengthen the bit-shift operators to use thin-tailed
arrowheads as you suggested.
I like this proposal for its
On 11/13/06, Darren Duncan [EMAIL PROTECTED] wrote:
- There are no Undef or NaN etc values or variables.
A RDBMS language with no null would seem to be problematic..
although i guess you could just use 1-tuples where the empty tuple is
treated as null.
--
Mark J. Reed [EMAIL PROTECTED]
HaloO,
Darren Duncan wrote:
What is the point of declaring a type as Rectangle, with those
limitations, if you are going to mutate it into not being a Rectangle.
There are three issues:
1) the subtyping relation
2) the preservation of object identity
3) the mutating add_vertex method
Would anyone be inconvenienced if the set_pmc vtable and the
setref and deref opcodes were removed? Note that if you are using set
_pmc but are not using assign_pmc, then you may not be
inconvenienced because right now the default assign_pmc vtable calls set_pmc.
These opcodes were added to
And you may be forced to deal with NaN and Inf values if you are storing raw
binary float values as they are built into the bit patterns.
--
Mark Biggar
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-- Original message --
From: Mark J. Reed [EMAIL
TSa writes:
Darren Duncan wrote:
For the record, my preference is to have the generics be the
shortest, [==,!==,=,,,=,=], and use [+,~] prefixes for Num or
Str casting versions. And lengthen the bit-shift operators to use
thin-tailed arrowheads as you suggested.
I like this proposal
Author: larry
Date: Mon Nov 13 10:14:35 2006
New Revision: 13475
Modified:
doc/trunk/design/syn/S03.pod
Log:
Added missing generic boolean comparisons as noted by dduncan++.
Modified: doc/trunk/design/syn/S03.pod
==
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #40863]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40863
Tcl currently has this code in pge2past.tg:
$S0 = node['decimal']
$I0
On 11/13/06, SADAHIRO Tomoyuki [EMAIL PROTECTED] wrote:
On Sat, 11 Nov 2006 16:34:55 -0800, Chip Salzenberg (via RT) wrote
because the Perl sprintf test suite seems to think that the right value
for sprintf('%e',1) is 1e+00, but Win32 seems to return 1e+000 (note
the extra digit in the
Am Montag, 13. November 2006 03:56 schrieb Bob Rogers:
+There are two techniques for implementing dynamic binding. These are
+traditionally called deep binding and shallow binding [2].
Can you please consider the impacts of a third variant using STM, which is
already implemented:
$ cat
I'm going to make the next release in the next day or two. I've compiled
what is no doubt a partial list of features and other achievements in the
NEWS file in the svn repo. Please check this for completeness and mail me
anything I've left out. (Copy the list if you like.)
Here for your
# New Ticket Created by Chip Salzenberg
# Please include the string: [perl #40865]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40865
The C standard says that the isxxx() and toxxx() functions are only defined
if
Smylers wrote:
Bzzzt, wrong language!
But Perl isn't an orthogonal language, it's a diagonal language.
http://www.oreilly.com/catalog/pperl2/excerpt/ch01.html
In the section quoted, it was indicated that orthogonal and
diagonal are being used to mean minimalist and loaded with
At 11:00 AM -0500 11/13/06, Mark J. Reed wrote:
On 11/13/06, Darren Duncan [EMAIL PROTECTED] wrote:
- There are no Undef or NaN etc values or variables.
A RDBMS language with no null would seem to be problematic..
although i guess you could just use 1-tuples where the empty tuple is
treated
Darren Duncan writes:
1. I'm not sure if it is possible yet, but like Haskell et al ..., it
should be possible to write a Perl 6 routine or program in a pure
functional notation or paradigm, such that the entire routine body is
a single expression, but that has named reusable sub-expressions.
On Nov 13, 2006, at 8:31 AM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40861]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40861
The
Andy, would you accept a patch for this to optionally allow things like:
FIXME (#40123)
but not:
FIXME
Which would allow us to let this slide if someone already opened a
ticket on it? (Probably want to specify the option as an RE)
On Nov 13, 2006, at 7:26 PM, Chris Dolan wrote:
On Nov
On Nov 13, 2006, at 7:14 PM, Will Coleda wrote:
Andy, would you accept a patch for this to optionally allow things
like:
FIXME (#40123)
No, I don't want to build in exceptions.
However, how about if the RT tickets are noted as RT #40123, which
is just as easy to find?
--
Andy Lester
Author: larry
Date: Mon Nov 13 17:09:46 2006
New Revision: 13476
Modified:
doc/trunk/design/syn/S03.pod
Log:
Add infix min and max as form of || to enable meta mods like min= or »max«
Modified: doc/trunk/design/syn/S03.pod
At 11:24 PM + 11/13/06, Smylers wrote:
Darren Duncan writes:
1. I'm not sure if it is possible yet, but like Haskell et al ..., it
should be possible to write a Perl 6 routine or program in a pure
functional notation or paradigm, such that the entire routine body is
a single
From: Leopold Toetsch [EMAIL PROTECTED]
Date: Mon, 13 Nov 2006 21:19:26 +0100
Am Montag, 13. November 2006 03:56 schrieb Bob Rogers:
+There are two techniques for implementing dynamic binding. ?These are
+traditionally called deep binding and shallow binding [2].
Can you
On Mon, Nov 13, 2006 at 07:33:18PM -0800, [EMAIL PROTECTED] wrote:
Log:
Fix size mismatch errors, at least on Linux/PPC. If this breaks
other platforms, there's a deeper bug somewhere and we need to
rethink t/tools/pbc_merge.t for the release.
Alas, it seems to break Linux/x86_64 --
On Monday 13 November 2006 21:49, Patrick R. Michaud wrote:
On Mon, Nov 13, 2006 at 07:33:18PM -0800, [EMAIL PROTECTED] wrote:
Log:
Fix size mismatch errors, at least on Linux/PPC. If this breaks
other platforms, there's a deeper bug somewhere and we need to
rethink t/tools/pbc_merge.t
29 matches
Mail list logo
