Comment: TPF (Score 1) on 2010.06.27 13:40
Hello, Schwern
First, I think Coke is Will Coleda
Cheers
Hello, Schwern
First, I think Coke is Will Coleda
Cheers
Accordingly with the perlvar manpage, $@ is used for error messages produced by eval.
I would like to use it as a more general variable for error messages. When a function returns a string, there isn't much that can be done to return a error string. Probably returning a list, setting an object, nothing clean and simple as real perl code
Perl is complaining about a deep recursion on a subroutine. That is natural, as I have deep recursion
Now the question is: can I silence Perl on these warnings?
In my last post I was complaining about 'use encoding'. As suggested, I changed. Now, I am using just 'Encode' module, 'encode' function. But that is not working correctly as well.
Encode seems to have problems by itself.
Can't locate object method "renewed" via package "Encode::utf8" at
And this happens from time to time...
The truth is that I tried to not use the encoding pragma. I do not like it as well. I prefer to binmode file handles and normally that works.
But with CGIs I get some problems. First, I am not able to binmode Template Toolkit when it opens templates. Or at least I can't find documentation on that.
The other problem is how to control the encoding from the environment variables, from CGI param and other stuff like that. But for these I think my current solution uses Encode already.
I'll fight with this script later today.
I am trying to use CGI::Session (and of course, CGI::Cookie) together with 'use encoding "utf-8"', but things seems not to work.
The error is 'Can't locate object method "renewed" via package "Encode::utf8" at
For some time that Perl modules are numbered with a major version, a minor version, and sometimes, a alpha/beta numbering.
Lately some modules adopted the usage of a serialized date. One of the latest was Regexp::Common. Do not stress, Abigail, nothing against it.
Now, the question are: is it useful? Should it be used just for old and stable modules like Regexp::Common or should we use it from the beginning?
I was really wondering.
A friend told me that current solution to Perl 6 taking so long, would be taking Perl 5.10.0 or Perl 5.12.0 and call it Perl 6.
The real new Perl 6 currently in development would get the sequential number of the previous in existence.
Hey, Nick.
I knew you are always dealing with the next Perl. But... version 10?
I know this is bad, to have a lot of working changing the webpage design, and the first comment is, bring the old back.
Unfortunately I agree with daxim. This design is too heavy (in colors and distracting boxes) for documentation, and too narrow (when we all have panoramic screens.
I think the old design was cool.
Before finishing, just as an external example, look at http://www.gtk.org/ . The main page have lots of collors, and fixed width, but when you get to the documentation ( http://library.gnome.org/devel/glib/stable/glib-Miscellaneous-Utility-Functions
And to finish, thank you for your dedication to http://perldoc.perl.org./ I think it is relevant and useful. But as well, I think constructive comments are helpful.
Cheers, Alberto
I still did not get the grip on Encodings and Perl. I have an UTF8 file that I want to process. This process calls a module that I know uses a bidirectional pipe with an latin1 process. But that should be hidden...