Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 630889FA0C4 for ; Thu, 26 Oct 2006 15:07:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 88864-07 for ; Thu, 26 Oct 2006 18:07:08 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.envysolutions.com (mark.mielke.cc [206.248.142.186]) by postgresql.org (Postfix) with ESMTP id 739209F935B for ; Thu, 26 Oct 2006 15:07:08 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.envysolutions.com (Postfix) with ESMTP id 0FA1C5404B; Thu, 26 Oct 2006 14:07:07 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.envysolutions.com Received: from mail.envysolutions.com ([127.0.0.1]) by localhost (mark.mielke.cc [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dANVQn67OG0E; Thu, 26 Oct 2006 14:07:06 -0400 (EDT) Received: by mail.envysolutions.com (Postfix, from userid 500) id E34475404C; Thu, 26 Oct 2006 14:07:06 -0400 (EDT) Date: Thu, 26 Oct 2006 14:07:06 -0400 From: mark@mark.mielke.cc To: Richard Troy Cc: Carlo Stonebanks , pgsql-performance@postgresql.org Subject: OT: TCL vs Perl Re: commit so slow program looks frozen Message-ID: <20061026180706.GA14287@mark.mielke.cc> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.094 tagged_above=0 required=5 tests=FORGED_RCVD_HELO, NO_REAL_NAME, SPF_HELO_PASS, SPF_PASS X-Spam-Level: * X-Archive-Number: 200610/558 X-Sequence-Number: 21687 Perl started out fast - TCL started out slow. Perl used syntax that, although it would drive some people crazy, followed a linguistic curve that Larry Wall claimed was healthy. The English language is crazy, and yet, it has become standard world wide as well. Designed, regular languages like Esperanto have not received much support either. Perl is designed to be practical. TCL was designed to be minimalistic. Perl uses common idioms for UNIX programmers. // for regular expressions, $VAR for variables, Many of the statement are familiar for C programmers. ++ for increment (compare against 'incr abc' for TCL). $a=5 for assignment, compare against 'set abc 5' in TCL. TCL tries to have a reduced syntax, where 'everything is a string' which requires wierdness for people. For example, newline is end-of-line, so { must be positioned correctly. Code is a string, so in some cases you need to escape code, otherwise not. Perl has object oriented support built-in. It's ugly, but it works. TCL has a questionable '[incr tcl]' package. Perl has a wealth of modules on CPAN to do almost anything you need to. TCL has the beginning of one (not as rich), but comes built-in with things like event loops, and graphicals (Tk). I could go on and on - but I won't, because this is the PostgreSQL mailing list. People either get Perl, or TCL, or they don't. More people 'get' Perl, because it was marketted better, it's syntax is deceivingly comparable to other well known languages, and for the longest time, it was much faster than TCL to write (especially when using regular expressions) and faster to run. Did TCL get treated unfairly as a result? It's a language. Who cares! :-) Cheers, mark -- mark@mielke.cc / markm@ncf.ca / markm@nortel.com __________________________ . . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder |\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ | | | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada One ring to rule them all, one ring to find them, one ring to bring them all and in the darkness bind them... http://mark.mielke.cc/