Re: TinyPerl 2.0 and new SF site.

[cchampion]

It is indeed a great feat. However ....

Is it really very stable?

Quoting from your sourceforge page:

• 01-05-2003

  TinyPerl 2.0 beta published. Now smaller, without need of the little directory ./lib and the XS of Compress::Zlib goes inside PerlLib (Perl58.dll).

  TinyPerl now can create binarys for your script too! ;-P

• 01-03-2003

  TinyPerl 1.1 released.

I wonder how could you tell in two days that a package as complex as Perl, albeit tiny is stable! Aren't you going too fast?

Now, I don't know about the innards of TinyPerl, but for example it doesn't run things like the Camel code. You may say that it is not the most useful piece of code in an enterprise or that it is not a fair example, but I would investigate why this worldwide known Perl script does not run.... :)¹

Cheers

cchampion

¹ Actually, it runs, but it doesn't print anything.

[PodMaster]

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.

[cchampion]

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.

[PodMaster]

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.

[gmpassos]

TinyPerl comes from the last release of standart Perl source. I got for version 2.0, ActivePerl source since it has some bug fixes of Perl 5.8.0

About the Camel code is because it reads the __DATA__ handle, and your script code was loaded inside a variable and paste to eval() to run! I can fix this in the next version opening the handle directly in you file code in the __DATA__ position.

About stability, this 2.0 version I was building before release TinyPerl 1.0 and 1.1. And they are the test of 2.0, since the 2.0 version changes only in the structure and bug fixes of 1.0/1.1! But we know that is impossible to make a real "stable" program or release! For example, when Perl 5.8.0 was released in my 1st test I got an error with Sockets, because they have implemented PerlIO with layer on Socket from default! And they tested this during a long long time!

I really releasede all the TinyPerl version because I have a lot o peoples asking me for this all the time! I can't leave this in my PC for more time if is useful for others!

Thanks for your reply, and bug report! ;-P

Graciliano M. P.
"The creativity is the expression of the liberty".