[29728] in Perl-Users-Digest
Perl-Users Digest, Issue: 972 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Oct 25 06:09:38 2007
Date: Thu, 25 Oct 2007 03:09:04 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Thu, 25 Oct 2007 Volume: 11 Number: 972
Today's topics:
(WWW.CNCIRCLE.COM) cheap wholease china men, women, ki <twwtcl@gmail.com>
Re: From "The Camel Book", Ch. 16 (IPC) xhoster@gmail.com
Re: From "The Camel Book", Ch. 16 (IPC) <jgibson@mail.arc.nasa.gov>
Re: From "The Camel Book", Ch. 16 (IPC) xhoster@gmail.com
Re: From "The Camel Book", Ch. 16 (IPC) <ben@morrow.me.uk>
Re: Implementation of file input operator <> himanshu.garg@gmail.com
new CPAN modules on Thu Oct 25 2007 (Randal Schwartz)
Re: TeX pestilence (was Distributed RVS, Darcs, tech lo <lasses_weil@klapptsowieso.net>
Re: TeX pestilence (was Distributed RVS, Darcs, tech lo <jurgenex@hotmail.com>
Re: TeX pestilence (was Distributed RVS, Darcs, tech lo <lasses_weil@klapptsowieso.net>
Re: TeX pestilence (was Distributed RVS, Darcs, tech lo <jo@durchholz.org>
Re: TeX pestilence <gernot@nict.go.jp>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 25 Oct 2007 02:47:06 -0700
From: kook <twwtcl@gmail.com>
Subject: (WWW.CNCIRCLE.COM) cheap wholease china men, women, kid's Jordan sneakers light AF1 shoes, ed hardy hooies, jeans , handbags, sunglass. Belts
Message-Id: <1193305626.385068.161880@t8g2000prg.googlegroups.com>
(www.cncircle.com ) are china Nike customs Shoes Wholesale design
company, we Wholesale NIKE Sneakers from our Nike factory to Nike
shop
& Nike store, sale and Wholesale all of Nike stock Shoes, we have
many
type of NIKE Sneakers : Nike discount Shoes, Nike cheap Shoes, Nike
stock Shoes (Nike Trainers, Nike Sneakers, Nike Running Shoes, Nike
Basketball Shoes,Nike Discount Shoes,Nike Cheap Shoes, footwear,
Sports Shoes )Wholesale Handbags Sneakers, Wholesale Purses,
Wholesale Sandals .nike shoes wholesale,wholesale nike shoes nike
shoes Nike Shox Sneaker Nike Max Sneaker Jordan Sneakers
Red Monkey Jeans Evisu jeans Rock & Republic Nike wholesale - Nike
shoes wholesale. Nike shoes: Nike shox air force1 jordan TL NZ R4,
We sale wholesale Nike shoes(Nike trainers, Nike sneakers, Nike nike
shoes tn gucci shoes air max shoes, handbags and purse sandals and
sunglasses jeans tshirt Nike Shoes Wholesale sizes include: Nike men's
Shoes, Nike women's Shoes, Nike mens Shoes, Nike womens Shoes, Nike
men Shoes, Nike women Shoes, Nike kids Shoes, Nike child Shoes.Nike
discount Shoes, Nike cheap Shoes, china Nike Shoes.
Our website: http://nikesneakertrade.photo.163.com and http://www.cncircle.com
(www.cncircle.com)sell ed hardy items included ed hardy caps,hats,ed
hardy mens,men's
womens women's shirts,t-shirts,100% contten at cheap and discount
price,popular brand Ed Hardy Hoodies&Jeans china wholesale,buy sell
and wholesale edhardy belt at (www.cncircle.com)
wholesale edhardy T-Shirts,Buy ed hardy T Shirt Online,Bulk wholesale
ed hardy T-shirts,sell edhardy T-Shirts Stock,ed hardy hoodies China
wholesaler,We are able to supply stock of Women's T-shirts,men's T-
shirts at cheap discounted discount price.
(www.cncircle.com)discount red monkey jeans
Cheap Nike Air Max Series Trainers From China Nike Outlet
(www.cncircle.com)Wholesale Nike Shox Nike Air Max Dunk Jordan
Cheap Discount shoes to nike shop & nike store from china nike
factory
(www.cncircle.com) ed hardy caps,ed hardy caps cheap,ed hardy
for cheap,ed hardy hats for cheap
(www.cncircle.com) will give you everything that you need regarding
cheap t shirts,discount t-shirts.If you think that you are willing to
start up your own home distribution business
then(www.cncircle.com)should be the first place that you visit.we sell
bulk orders and we
are willing to do best service for you.
------------------------------
Date: 24 Oct 2007 22:25:33 GMT
From: xhoster@gmail.com
Subject: Re: From "The Camel Book", Ch. 16 (IPC)
Message-Id: <20071024182536.288$VV@newsreader.com>
rihad <rihad@mail.ru> wrote:
> Chapter 16 "Interprocess Communication" of "Programming Perl" has this
> part:
What edition of the book?
>
> use Fcntl ':flock';
> eval {
> local $SIG{ALRM} = sub { die "alarm clock restart" };
> alarm 10; # schedule alarm in 10 seconds
> eval {
> flock(FH, LOCK_EX) # a blocking, exclusive lock
> or die "can't flock: $!";
> };
> alarm 0; # cancel the alarm
> };
> alarm 0; # race condition protection
> die if $@ && $@ !~ /alarm clock restart/; # reraise
This just doesn't make sense to me in the first place. What is the purpose
if the inner eval? The "can't flock: $!" message is useless, as the inner
eval is never tested against failure directly and the outer eval will
stomp on the $@ set by the inner eval. Similarly, the error raised by
$SIG{ALRM} is overwhelmingly likely to occur inside the inner eval,
so the test of $@ outside both evals is not going to detect the time out,
which seems to be its sole purpose.
Xho
--
-------------------- http://NewsReader.Com/ --------------------
The costs of publication of this article were defrayed in part by the
payment of page charges. This article must therefore be hereby marked
advertisement in accordance with 18 U.S.C. Section 1734 solely to indicate
this fact.
------------------------------
Date: Wed, 24 Oct 2007 17:50:43 -0700
From: Jim Gibson <jgibson@mail.arc.nasa.gov>
Subject: Re: From "The Camel Book", Ch. 16 (IPC)
Message-Id: <241020071750439356%jgibson@mail.arc.nasa.gov>
In article <20071024182536.288$VV@newsreader.com>, <xhoster@gmail.com>
wrote:
> rihad <rihad@mail.ru> wrote:
> > Chapter 16 "Interprocess Communication" of "Programming Perl" has this
> > part:
>
> What edition of the book?
>
> >
> > use Fcntl ':flock';
> > eval {
> > local $SIG{ALRM} = sub { die "alarm clock restart" };
> > alarm 10; # schedule alarm in 10 seconds
> > eval {
> > flock(FH, LOCK_EX) # a blocking, exclusive lock
> > or die "can't flock: $!";
> > };
> > alarm 0; # cancel the alarm
> > };
> > alarm 0; # race condition protection
> > die if $@ && $@ !~ /alarm clock restart/; # reraise
>
> This just doesn't make sense to me in the first place. What is the purpose
> if the inner eval? The "can't flock: $!" message is useless, as the inner
> eval is never tested against failure directly and the outer eval will
> stomp on the $@ set by the inner eval. Similarly, the error raised by
> $SIG{ALRM} is overwhelmingly likely to occur inside the inner eval,
> so the test of $@ outside both evals is not going to detect the time out,
> which seems to be its sole purpose.
3rd Edition, p. 417:
"The nested exception trap is included because calling flock would
raise an exception if flock is not implemented on your platform, and
you need to make sure to clear the alarm anyway. The second alarm 0 is
provided in case the signal comes in after running the flock but before
getting to the first alarm 0."
--
Jim Gibson
Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com
------------------------------
Date: 25 Oct 2007 01:18:34 GMT
From: xhoster@gmail.com
Subject: Re: From "The Camel Book", Ch. 16 (IPC)
Message-Id: <20071024211837.919$HG@newsreader.com>
Jim Gibson <jgibson@mail.arc.nasa.gov> wrote:
> In article <20071024182536.288$VV@newsreader.com>, <xhoster@gmail.com>
> wrote:
>
> > rihad <rihad@mail.ru> wrote:
> > > Chapter 16 "Interprocess Communication" of "Programming Perl" has
> > > this part:
> >
> > What edition of the book?
> >
> > >
> > > use Fcntl ':flock';
> > > eval {
> > > local $SIG{ALRM} = sub { die "alarm clock restart" };
> > > alarm 10; # schedule alarm in 10 seconds
> > > eval {
> > > flock(FH, LOCK_EX) # a blocking, exclusive lock
> > > or die "can't flock: $!";
> > > };
> > > alarm 0; # cancel the alarm
> > > };
> > > alarm 0; # race condition protection
> > > die if $@ && $@ !~ /alarm clock restart/; # reraise
> >
> > This just doesn't make sense to me in the first place. What is the
> > purpose if the inner eval? The "can't flock: $!" message is useless,
> > as the inner eval is never tested against failure directly and the
> > outer eval will stomp on the $@ set by the inner eval. Similarly, the
> > error raised by $SIG{ALRM} is overwhelmingly likely to occur inside the
> > inner eval, so the test of $@ outside both evals is not going to detect
> > the time out, which seems to be its sole purpose.
>
> 3rd Edition, p. 417:
>
> "The nested exception trap is included because calling flock would
> raise an exception if flock is not implemented on your platform,
Isn't that something you would want to know? Why go to the trouble
of constructing a decent die string if it will never be seen?
And why test for "alarm clock restart" in such a way that vast majority
of such restarts won't be detected by the test?
> and
> you need to make sure to clear the alarm anyway. The second alarm 0 is
> provided in case the signal comes in after running the flock but before
> getting to the first alarm 0."
Presumably that means "after exiting the inner eval but before
getting to the first alarm 0". But I don't see that that makes much
sense, either. Once the alarm has fired, there is no need to
turn it off--it is already off. At least on my system. Are there
systems where alarm keeps re-installing itself for the original interval,
rather than being a one-shot deal?
Xho
--
-------------------- http://NewsReader.Com/ --------------------
The costs of publication of this article were defrayed in part by the
payment of page charges. This article must therefore be hereby marked
advertisement in accordance with 18 U.S.C. Section 1734 solely to indicate
this fact.
------------------------------
Date: Thu, 25 Oct 2007 02:56:07 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: From "The Camel Book", Ch. 16 (IPC)
Message-Id: <nm95v4-99c.ln1@osiris.mauzo.dyndns.org>
Quoth rihad <rihad@mail.ru>:
> Chapter 16 "Interprocess Communication" of "Programming Perl" has this
> part:
>
> use Fcntl ':flock';
> eval {
> local $SIG{ALRM} = sub { die "alarm clock restart" };
> alarm 10; # schedule alarm in 10 seconds
> eval {
> flock(FH, LOCK_EX) # a blocking, exclusive lock
> or die "can't flock: $!";
> };
> alarm 0; # cancel the alarm
> };
> alarm 0; # race condition protection
> die if $@ && $@ !~ /alarm clock restart/; # reraise
It should be noted that this won't work under 5.8 with 'safe signals',
as $SIG{ALRM} won't be called until after flock returns (which is
exactly what you're trying to avoid). This can be worked around with
POSIX::SigAction.
Ben
------------------------------
Date: Thu, 25 Oct 2007 05:49:07 -0000
From: himanshu.garg@gmail.com
Subject: Re: Implementation of file input operator <>
Message-Id: <1193291347.062925.303490@k35g2000prh.googlegroups.com>
On Oct 25, 1:58 am, Ben Morrow <b...@morrow.me.uk> wrote:
> Quoth himanshu.g...@gmail.com:
>
>
>
> > Could you tell me which file in the perl source distro I should
> > look at for the implementation of the file input operators <>.
>
> <> is implemented as pp_readline in pp_hot.c, which calls
> pp_hot.c:Perl_do_readline, which calls sv.c:Perl_sv_gets, which calls
> PerlIO_read to perform the actual read. Note that understanding the Perl
> IO system is not easy.
>
> > I suspect that one 'call' of <> is leading to two read system
> > calls.
>
> As Uri pointed out, this is expected and desired. If you want to do your
> own buffering, push a :unix layer or use sysread.
>
Thanks Uri and Ben,
There was a race condition in which the child process died during
the second read call and the parent kept waiting. Using a signal
handler for SIGCHLD required many code changes. Using sysread, I no
longer see the error.
Since multiple reads are entirely possible I will not go into the
source :)
Thank You,
HG
------------------------------
Date: Thu, 25 Oct 2007 04:42:15 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Thu Oct 25 2007
Message-Id: <JqGAEF.21I@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Acme-ProgressBar-1.122
http://search.cpan.org/~rjbs/Acme-ProgressBar-1.122/
a simple progress bar for the patient
----
Amce-CNA-0.062
http://search.cpan.org/~rjbs/Amce-CNA-0.062/
a moer tolernat verison of mehtod location
----
App-Addex-0.009
http://search.cpan.org/~rjbs/App-Addex-0.009/
generate mail tool configuration from an address book
----
Astro-SpaceTrack-0.030
http://search.cpan.org/~wyant/Astro-SpaceTrack-0.030/
Retrieve orbital data from www.space-track.org.
----
CORBA-IDL-2.62
http://search.cpan.org/~perrad/CORBA-IDL-2.62/
----
CPAN-Reporter-1.03
http://search.cpan.org/~dagolden/CPAN-Reporter-1.03/
Adds CPAN Testers reporting to CPAN.pm
----
CPANPLUS-Dist-Mdv-0.1.3
http://search.cpan.org/~jquelin/CPANPLUS-Dist-Mdv-0.1.3/
a cpanplus backend to build mandriva rpms
----
CatalystX-CRUD-0.04
http://search.cpan.org/~karman/CatalystX-CRUD-0.04/
CRUD framework for Catalyst applications
----
Clarion-1.1_2.2
http://search.cpan.org/~ukoloff/Clarion-1.1_2.2/
Perl module for reading CLARION 2.1 data files
----
Class-Accessor-Complex-0.10
http://search.cpan.org/~marcel/Class-Accessor-Complex-0.10/
arrays, hashes, booleans, integers, sets and more
----
Class-Accessor-Constructor-0.04
http://search.cpan.org/~marcel/Class-Accessor-Constructor-0.04/
constructor generator
----
Class-Accessor-FactoryTyped-0.02
http://search.cpan.org/~marcel/Class-Accessor-FactoryTyped-0.02/
accessors whose values come from a factory
----
Clone-Closure-0.02
http://search.cpan.org/~bmorrow/Clone-Closure-0.02/
A clone that knows how to clone closures
----
Config-Model-CursesUI-1.004
http://search.cpan.org/~ddumont/Config-Model-CursesUI-1.004/
Curses interface for configuration tree
----
Config-Model-Xorg-0.505
http://search.cpan.org/~ddumont/Config-Model-Xorg-0.505/
Xorg configuration model for Config::Model
----
Coro-4.13
http://search.cpan.org/~mlehmann/Coro-4.13/
coroutine process abstraction
----
Devel-Declare-0.001003
http://search.cpan.org/~mstrout/Devel-Declare-0.001003/
----
Devel-TraceINC-0.01
http://search.cpan.org/~marcel/Devel-TraceINC-0.01/
trace who is loading which perl modules
----
Device-SerialPort-1.04
http://search.cpan.org/~cook/Device-SerialPort-1.04/
Linux/POSIX emulation of Win32::SerialPort functions.
----
FCGI-IIS-0.05
http://search.cpan.org/~cosmicnet/FCGI-IIS-0.05/
FCGI wrapper for MS IIS FastCGI
----
File-BaseDir-0.03
http://search.cpan.org/~pardus/File-BaseDir-0.03/
Use the Freedesktop.org base directory specification
----
File-Path-2.02
http://search.cpan.org/~dland/File-Path-2.02/
Create or remove directory trees
----
Games-Hack-Live-0.4
http://search.cpan.org/~pmarek/Games-Hack-Live-0.4/
Perl script to ease playing games
----
Games-Hack-Patch-i686-0.4
http://search.cpan.org/~pmarek/Games-Hack-Patch-i686-0.4/
How to patch code sequences on i686
----
Geo-Ov2-0.90_03
http://search.cpan.org/~hpa/Geo-Ov2-0.90_03/
Library for reading and writing TomTom Navigator .ov2 POI files.
----
HTML-Feature-2.0.1
http://search.cpan.org/~miki/HTML-Feature-2.0.1/
Extract Feature Sentences From HTML Documents
----
Image-ExifTool-7.00
http://search.cpan.org/~exiftool/Image-ExifTool-7.00/
Read and write meta information
----
Inline-Befunge-1.1.0
http://search.cpan.org/~jquelin/Inline-Befunge-1.1.0/
write Perl subs in Befunge
----
Language-Befunge-3.01
http://search.cpan.org/~jquelin/Language-Befunge-3.01/
a Befunge-98 interpreter
----
Logfile-EPrints-1.16
http://search.cpan.org/~timbrody/Logfile-EPrints-1.16/
Process Web log files for institutional repositories
----
Mail-Box-2.076
http://search.cpan.org/~markov/Mail-Box-2.076/
manage a mailbox, a folder with messages
----
Module-Build-0.2808_01
http://search.cpan.org/~kwilliams/Module-Build-0.2808_01/
Build and install Perl modules
----
Module-CPANTS-Analyse-v0.74
http://search.cpan.org/~domm/Module-CPANTS-Analyse-v0.74/
Generate Kwalitee ratings for a distribution
----
Module-CPANTS-ProcessCPAN-v0.70
http://search.cpan.org/~domm/Module-CPANTS-ProcessCPAN-v0.70/
Generate Kwalitee ratings for the whole CPAN
----
Module-CPANTS-Site-v0.70
http://search.cpan.org/~domm/Module-CPANTS-Site-v0.70/
Catalyst based application
----
Net-xFTP-0.17
http://search.cpan.org/~turnerjw/Net-xFTP-0.17/
Common wrapper functions for use with either Net::FTP or Net::xFTP.
----
Parse-Marpa-0.001_023
http://search.cpan.org/~jkegl/Parse-Marpa-0.001_023/
Earley's Algorithm, with improvements
----
QWizard-3.12
http://search.cpan.org/~hardaker/QWizard-3.12/
Display a series of questions, get the answers, and act on the answers.
----
SOAP-WSDL-2.00_22
http://search.cpan.org/~mkutter/SOAP-WSDL-2.00_22/
SOAP with WSDL support
----
String-BlackWhiteList-0.02
http://search.cpan.org/~marcel/String-BlackWhiteList-0.02/
match a string against a blacklist and a whitelist
----
TRL-Microarray-0.06
http://search.cpan.org/~cjones/TRL-Microarray-0.06/
A Perl module for creating and manipulating microarray objects
----
Test-Weaken-0.001_009
http://search.cpan.org/~jkegl/Test-Weaken-0.001_009/
Test for leaks after weakening of circular references
----
Test-Weaken-0.002001
http://search.cpan.org/~jkegl/Test-Weaken-0.002001/
Test for leaks after weakening of circular references
----
Text-CSV_XS-0.32
http://search.cpan.org/~hmbrand/Text-CSV_XS-0.32/
comma-separated values manipulation routines
----
Win32-IEHistory-0.03
http://search.cpan.org/~ishigaki/Win32-IEHistory-0.03/
parse Internet Explorer's history index.dat
----
XML-Tiny-1.07
http://search.cpan.org/~dcantrell/XML-Tiny-1.07/
simple lightweight parser for a subset of XML
----
version-0.74
http://search.cpan.org/~jpeacock/version-0.74/
Perl extension for Version Objects
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: Thu, 25 Oct 2007 00:38:31 +0200
From: Wildemar Wildenburger <lasses_weil@klapptsowieso.net>
Subject: Re: TeX pestilence (was Distributed RVS, Darcs, tech love)
Message-Id: <471fc967$0$13110$9b4e6d93@newsspool2.arcor-online.net>
Joachim Durchholz wrote:
> And yes, it sucks in major ways.
>
Oh my God, I don't want to, but I just have to ask: Why?
/W
------------------------------
Date: Wed, 24 Oct 2007 22:40:34 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: TeX pestilence (was Distributed RVS, Darcs, tech love)
Message-Id: <CRPTi.2859$f63.79@trndny03>
Wildemar Wildenburger wrote:
> Joachim Durchholz wrote:
>> And yes, it sucks in major ways.
>>
> Oh my God, I don't want to, but I just have to ask: Why?
Because TeX has nothing to do with either Perl, Python, Lisp, Java, or
functional programming.
jue
------------------------------
Date: Thu, 25 Oct 2007 00:52:52 +0200
From: Wildemar Wildenburger <lasses_weil@klapptsowieso.net>
Subject: Re: TeX pestilence (was Distributed RVS, Darcs, tech love)
Message-Id: <471fccc5$0$27138$9b4e6d93@newsspool1.arcor-online.net>
Jürgen Exner wrote:
> Wildemar Wildenburger wrote:
>> Joachim Durchholz wrote:
>>> And yes, it [syntactically] sucks in major ways.
>>>
>> Oh my God, I don't want to, but I just have to ask: Why?
>
> Because TeX has nothing to do with either Perl, Python, Lisp, Java, or
> functional programming.
>
That's not an answer to my question and you know it.
But OK, F'up to c.l.tex (makes me wonder why Xah didn't ... well,
actually it doesn't, nevermind ;))
/W
------------------------------
Date: Thu, 25 Oct 2007 09:33:44 +0200
From: Joachim Durchholz <jo@durchholz.org>
Subject: Re: TeX pestilence (was Distributed RVS, Darcs, tech love)
Message-Id: <ffpgsb$nil$1@online.de>
Wildemar Wildenburger schrieb:
> Joachim Durchholz wrote:
>> And yes, it sucks in major ways.
>>
> Oh my God, I don't want to, but I just have to ask: Why?
First of all, irregularities.
http://en.wikipedia.org/wiki/TeX#The_typesetting_system:
"[...]almost all of TeX's syntactic properties can be changed on the fly
which makes TeX input hard to parse by anything but TeX itself."
Then: No locals.
In particular, processing is controlled via global flags. If you need a
different setting while a macro is processing, you have to remember to
reset it before macro exit.
Many packages just set the flags to a standard value.
In other words, if you didn't know that a specific flag affects the
operation of your macro, the macro may break when used with a different
package that sets the flag to a different default value. (This may be
one of the reasons why everybody just sticks with LaTeX.)
Four stages of processing, and you have to know exactly which is
responsible for what to predict the outcome of a macro.
This is more a documentation problem - for several features, there's no
description which stage is responsible for processing it. That can make
working with a feature difficult, since you don't know which processing
steps have already been done and which are still to happen.
My TeX days are long gone, so I may have forgotten some of the problems,
but I think these were the worst. (And, of course, I may have gotten
some details mixed up, so if you're seriously interested in the good and
bad sides of TeX, verify before taking anything for granted.)
Note that it's just the markup language that I object to. The
typesetting algorithms seem to be remarkably regular and robust.
I would have very much liked to see TeX split up into a typesetting
library and a language processor.
Unfortunately, that was beyond my capabilities at the time I came into
contact with TeX, and I never got around to revisiting the issue.
However, the TeX algorithm has been extracted and made available as a
Regards,
Jo
------------------------------
Date: Thu, 25 Oct 2007 10:09:24 +0900
From: Gernot Hassenpflug <gernot@nict.go.jp>
Subject: Re: TeX pestilence
Message-Id: <877ilcc857.fsf@nict.go.jp>
Charlton Wilbur <cwilbur@chromatico.net> writes:
>>>>>> "BB" == Brian Blackmore <blb8@po.cwru.edu> writes:
>
> BB> I find it very sad and, perhaps, very telling, that XL attacks
> BB> TeX on all the non-TeX newsgroups. This is, perhaps, strange?
>
> It's strange by the standards of reasonable Usenettery, insofar as
> such a thing exists, but Xah is well known for this kind of nonsense.
/../
> I wouldn't waste any more energy on Xah, unless it were expended
> adding him to your killfile.
Oh dear, I only knew it from its "how to improve Emacs" (to make it
more in line with MS Windows users' knowledge and expectations)
postings on the emacs newgroups. Morphing is just *so* wrong! Ha,
another killfile entry....
--
BOFH excuse #361:
Communist revolutionaries taking over the server room and demanding all the computers in the building or they shoot the sysadmin. Poor misguided fools.
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 972
**************************************
