http://www.perlmonks.org?node_id=225668


in reply to Re: TinyPerl 2.0 and new SF site.
in thread TinyPerl 2.0 and new SF site.

Stability is not an issue.

Tinyperl is as stable as perl itself is.

Camel Code does not run because it tries to read off the magical filehandle DATA. I'm sure this is due to a simple oversight by gmpassos (as soon as I get my hands on the sourcecode i'm pretty sure i'll be able to fix it)


MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
** The Third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re: Re: Re: TinyPerl 2.0 and new SF site.
by cchampion (Curate) on Jan 10, 2003 at 00:11 UTC

    Well, maybe there was more than one oversight... ;-)

    This code

    tinyperl -e "print <*>"

    generates a system error, while ActiveState Perl executes without a shrug.

    Don't misunderstand me. I am really thrilled about TinyPerl. It's just that I am cautious when embracing new software, and before saying that it is stable I usually wait until some bugs are reported.

      Same deal.
      perldoc -f glob glob EXPR glob Returns the value of EXPR with filename expansions such as + the standard Unix shell /bin/csh would do. This is the interna +l function implementing the "<*.c>" operator, but you can us +e it directly. If EXPR is omitted, $_ is used. The "<*.c>" oper +ator is discussed in more detail in "I/O Operators" in perlop. Beginning with v5.6.0, this operator is implemented using +the standard "File::Glob" extension. See File::Glob for detail +s.

      Being cautious is good, and i'm sure you knew about glob.


      MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
      ** The Third rule of perl club is a statement of fact: pod is sexy.