At 12:35 AM -0700 7/9/05, Jonathan Leffler wrote:
I dunno which DBMS support prepare without a database connection,
but I would expect all the mainstream databases to require a
database connection. IBM DB2 does; IBM Informix Dynamic Server
(IDS) does; someone else commented on this and said
On Fri, Jul 08, 2005 at 08:50:35AM -0500, Jonathan Scott Duff wrote:
On Fri, Jul 08, 2005 at 08:10:00AM +0200, Robin Redeker wrote:
And what will be the default syntax to call
a method on self? If everyone has completly other
preferences about this, for example this horrible ./method()
On Fri, Jul 08, 2005 at 08:50:35AM -0500, Jonathan Scott Duff wrote:
On Fri, Jul 08, 2005 at 08:10:00AM +0200, Robin Redeker wrote:
And what will be the default syntax to call
a method on self? If everyone has completly other
preferences about this, for example this horrible ./method()
On Fri, Jul 08, 2005 at 10:07:24AM -0400, Stevan Little wrote:
On Jul 8, 2005, at 2:10 AM, Robin Redeker wrote:
And what will be the default syntax to call
a method on self? If everyone has completly other
preferences about this, for example this horrible ./method()
syntax, which completly
In other words, Huffman coding works and Perl6 hackers had better start
watching their waistlines. Or maybe we should spin it that Perl6 helps
reduce global warming ;)
Anyway, I collected a small sample (~300 lines each) of Perl5 code along
with equivalent Perl6 code. Some came from the
Still late to the party - another one bullet point item...
On 7/4/05, Darren Duncan [EMAIL PROTECTED] wrote:
4. All host parameters should be named (like :foo) rather than
positional (like ?), meeting with the SQL:2003 standard. The named
format is a lot easier to use and flexible, making
At 1:03 AM -0700 7/9/05, Jonathan Leffler wrote:
Can you explain which parts of the SQL:2003 mandate this notation?
I've had a moderately good poke around my copy of ISO/IEC
9075-2:2003 (SQL/Foundation) and cannot find this. I'd like a few
section numbers listed which describe this.
The
At 1:22 AM -0700 7/9/05, Jonathan Leffler wrote:
On 7/4/05, Darren Duncan
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] wrote:
5. All details used to construct a connection handle should be
completely decomposed rather than shoved into an ungainly data
source. Examples of what should be distinct
Wolverian wrote:
On Thu, Jul 07, 2005 at 05:58:53PM -0700, Larry Wall wrote:
$fh.pos = $fh.pos + 10`lines
I'm sorry if this has been discussed, but is the ` going to be in
Perl 6? I like it. :)
I was hoping it was going to be in the standard library, but non-core.
Using it for
Jared Still wrote:
I use a (Perl) password server for this.
Passwords are stored encrypted in a configuration file.
Clients authenticate with the server, and receive a requested
password (encrypted) across the network, if the client is
entitled.
The user authentication is rudimentary, but it
Late to the ball - and only picking up on one issue...
On 7/4/05, Darren Duncan [EMAIL PROTECTED] wrote:
2. Always separate out any usage stages that can be performed apart
from the database itself. This allows an application to do those
stages more efficiently, consuming fewer resources of
On Fri, Jul 08, 2005 at 08:28:34PM +0200, Robin Redeker wrote:
: On Fri, Jul 08, 2005 at 10:07:24AM -0400, Stevan Little wrote:
: I have never understood what is wrong with this:
:
: method foo ($self: $bar) {
: $self.baz()
: }
:
: Thats a fine option to have.
: But therecomes another
On Fri, Jul 08, 2005 at 05:43:01PM +0200, Robin Redeker wrote:
: Maybe per .-file in the home-directory, like .vimrc ...
Only if pulled in with a use. I don't want to see Perl programs
implicitly starting in a variant language. Dialects must be declared.
Otherwise you're in a situation like
In Pugs's ext/Set/lib/Set.pm, there are a number of user-defined
infix operators. To avoid unicode in mails, I'll use a hypothetical
infix:=== as the operator name.
Consider the sub case:
class Set;
sub infix:=== (Set $x, Set $y) { ... }
Is it correct that this line:
Set.new ===
On Sat, Jul 09, 2005 at 11:34:23PM +0800, Autrijus Tang wrote:
: In Pugs's ext/Set/lib/Set.pm, there are a number of user-defined
: infix operators. To avoid unicode in mails, I'll use a hypothetical
: infix:=== as the operator name.
We've intentionally been using Unicode in this mailing list on
Larry wrote:
I would like to point out that for mere mortals, *any* MMD is already too
complex to be predictable.
This is the relevant observation here.
This particular mortal's experience is that more than four variants, involving
parameters from more than two hierarchies makes it nearly
Jonathan, while you are well-meaning in your comments, you are
mis-reading what I have said multiple times and are therefore making
a straw man argument against it.
Regarding this point:
5. All details used to construct a connection handle should be
completely decomposed rather than shoved
17 matches
Mail list logo
