On Fri, 5 Oct 2001, Mark J. Reed wrote:
> Well, "car" and "cdr" don't really fit; the key and value of a pair can be any
> type of object, unlike the Lisp case where the cdr is always a list
> (while the car can be either a list or an atom).
Incorrect - "cdr" can be anything at all, just like
Can I get a .car and a .cdr please? In my limited mind "key" and "value"
are specific to hashes and their wimpy brother associative lists.
-sam
Can I get a what what?
On Thu, 4 Oct 2001, Damian Conway wrote:
> A false economy. We should encourage Larry as often as we can.
> After all, is it any wonder that it's so long between Apocalypses when
> every time he releases one, he gets nothing but negative feedback?
Hm, that never occured to me. In that case, let
On Wed, 29 Aug 2001, Jeremy Howard wrote:
> The answer used in .NET is to have a dispose() method (which is not a
> special name--just an informal standard) that the class user calls manually
> to clean up resources. It's not an ideal solution but there doesn't seem to
> be many other practical o
On Mon, 9 Jul 2001, Dan Brian wrote:
> "program XSLT in XML"? What does that mean?
It means roughly what "program Perl in ASCII" means.
> Have you used XSLT? Do you understand what it is and what it does? It
> makes quite a bit of sense for those performing regular conversions
> from a single
On Mon, 9 Jul 2001, Adam Turoff wrote:
> Who said programming Perl in XML was a good idea?
Did you read the article I was responding to? I suggest you do.
Strangely, many people seem to believe XML is ideally suited to every
computing task known to man. This includes programming in Perl,
appar
On Mon, 9 Jul 2001, Adam Turoff wrote:
> Don't laugh. It's here now. It's called XSLT. :-)
Um, that's not what the article was talking about The proposal is to use
an XML syntax to program in existing "VHLL" languages, including Perl.
This would supposedly allow programmers to embed drawings
On Mon, 9 Jul 2001, ivan wrote:
> http://www.ora.com/news/vhll_1299.html
Fascinating article, but his point about XML source code struck my funny
bone. I've certainly heard the argument before - most recently in Dr.
Dobbs Software Development insert.
I've got just one question: if this is such
On Sun, 10 Jun 2001, Me wrote:
> Agreed. So long as you are talking about Perl 5's arrays.
>
> I disagree, if you are talking about 2 dimensional structures.
You appear to have some fundamental misunderstanding about Perl 5. Perl 5
does indeed support multidimentional arrays:
my @matrix = (
On Sun, 10 Jun 2001, Me wrote:
> Yes. But if the syntax for arrays and db data are to
> be simultaneously the same and as ideal as possible,
> then either the core array syntax needs to be relatively
> ideal for relational db data, or one needs to redefine
> the array syntax to match a created db
On Thu, 10 May 2001, David Grove wrote:
> The changes are beautiful. It's calling it "Perl" and relying on subliminal
> pursuasion to ask users to consider it the same that bothers me. That's a
> very Microsoftish tactic.
No, it's "Perl 6". If you want "Perl 5" or even "Perl 4" you know where
t
On Wed, 21 Feb 2001 [EMAIL PROTECTED] wrote:
> On Wed, Feb 21, 2001 at 05:32:50PM -0500, Sam Tregar wrote:
> > Examples? I know you're not talking about C or C++. I'm pretty sure
> > you're not talking about Java - exception-handling renders the term "
On Wed, 21 Feb 2001, Bart Lateur wrote:
> Actually, it's pretty common. Only, most languages are not as forgiving
> as perl, and what is merely a warning in Perl, is a fatal error in those
> languages. Trying to read the value of an uninitialized variable, for
> example, that's commonly a fatal e
On Mon, 12 Feb 2001, Dan Sugalski wrote:
> >I think I've heard you state that before. Can you be more specific? What
> >alternate system do you have in mind? Is this just wishful thinking?
>
> This isn't just wishful thinking, no.
You picked the easy one. Maybe you can get back to the other
On Mon, 12 Feb 2001, Dan Sugalski wrote:
> Perl needs some level of tracking for objects with finalization attached to
> them. Full refcounting isn't required, however.
I think I've heard you state that before. Can you be more specific? What
alternate system do you have in mind? Is this just
On Sun, 11 Feb 2001, Jan Dubois wrote:
> However, I couldn't solve the problem of "deterministic destruction
> behavior": Currently Perl will call DESTROY on any object as soon as the
> last reference to it goes out of scope. This becomes important if the
> object own scarce external resources (
On Fri, 15 Dec 2000, Jarkko Hietaniemi wrote:
> Limbo, the systems programming language of Inferno, nee Plan 9, nee UNIX.
>
> http://www.vitavuova.com/inferno/papers/limbo.html
What are your thoughts about Limbo? I did some Limbo programming a couple
of years back. I can't say I came out of th
On Tue, 19 Sep 2000, Glenn Linderman wrote:
> > I agree that undef and NULL have different semantics. However, this is
> > clearly SQL's fault and not Perl's. We shouldn't repeat their mistake
> > just because we occasionally have to interface with their system.
>
> They are different. Neithe
On 20 Sep 2000, Perl6 RFC Librarian wrote:
> The absence of a C concept and keyword in Perl makes it more
> difficult to interface with relational databases and other medium which
> utilize C. Modules such as C must map C to C,
> which is an imperfect match.
Does it really make it more difficult
On Tue, 19 Sep 2000, Dave Storrs wrote:
> "Unpack takes binary data in some particular format and
> disassembles it, assigning various pieces of it to variables according to
> formatting that you supply. Pack does the opposite, using your supplied
> formatting to crunch Perl scalar variabl
On 19 Sep 2000, Perl6 RFC Librarian wrote:
> Distinguish packed binary data from printable strings
What defines a "printable" string? What if I'm working in an environment
that can "print" bytes that yours can't? Specifically I'm wondering how
this proposal handles Unicode.
-sam
On Mon, 18 Sep 2000, Michael G Schwern wrote:
> On Mon, Sep 18, 2000 at 12:32:08PM -0400, Sam Tregar wrote:
>
> If I grok'd the bastards, I'd write the explaination myself.
If you grok'd the bastards I bet you'd realize how useless such an
explanation would be. Th
On Mon, 18 Sep 2000, Michael G Schwern wrote:
> Perhaps someone could attempt to write an explaination of pack and
> unpack in completely Perl terms. No bits, no ints, no nybbles, no
> IEEE floating point arithmetic, no prior knowledge of C necessary.
> Those are not Perl. Scalars, arrays, hash
On Thu, 31 Aug 2000, David L. Nicol wrote:
> We're talking about making a faster Perl. C's syntax requires enough
> clarity to compile to something quick. it is a very short hop from
> my dog $spot;
> to
> dog spot;
What about the second version would result in faster execution? D
On Thu, 31 Aug 2000, David L. Nicol wrote:
> Perl looks, and AFAIK has always looked, like "C plus lune noise" to
> many people.
I think Perl looks like "C plus moon noise" to former C programmers. I
imagine some people see it and think "Csh plus Awk noise". Perl is a lot
more than C-with-scal
On 23 Aug 2000, Perl6 RFC Librarian wrote:
> Since versioning is a meta-implementation issue, all that is required
> is that fearless leader has to agree this is a good idea.
Very funny. I suppose you don't mind if he changes his mind someday?
I'm starting to think that you have too much time
On Wed, 2 Aug 2000, Ala Qumsieh wrote:
> Also, how about renaming my() to local()? Will this be too confusing?
Yes, that would be too confusing.
-sam
On 2 Aug 2000, Gisle Aas wrote:
> =head1 PERL5 PORTABILITY
>
> Calls to time() could be transformed to int(time()) when converting
> perl5 programs to perl6.
Unless there's a:
use HiRes::Time qw(time);
in effect!
-sam
On Tue, 1 Aug 2000, Buddha Buck wrote:
> I haven't looked at the internals for local, but isn't:
Nope. Local works on globals and "$unnamed_foo" isn't a lexical, its a
global available inside called functions. So when you call
uses_foo() from within the block it will see the local value of $fo
29 matches
Mail list logo
