[Mastering-perl] Check out the chapters on configuration, subroutines, and Pod

[Derek B. Smith]

-- Florian Merges <fmerges at cpan.org> wrote:

> Hi,
> 
> 2006/9/21, Derek B. Smith
> <derekbellnersmith at yahoo.com>:
> >
> > ok brian, again, thank you for replying.
> > One thing I did notice that I forgot to mention. I
> > noticed in some of your code you DID NOT use "best
> > practice" in some blocks of code. For example an
> if
> > construct you used
> > if ( /string/ )
> > {
> >     print "foo\n";
> > }
> >
> > Remembering the text from Best Practices, you guys
> > stated do not cuddle if or else statments on new
> > lines. For example best practice would be:
> >
> > if ( /string/ ) {
> >     print "foo\n";
> > }
> > else {
> >     print "foo-bar\n";
> > }
> >
> > I know its a small thing but if its titled
> Matering
> > Perl than many concepts/practices such as the one
> > above should should reflect or follow whats in
> Perl
> > Best practices, right?
> 
> 
> 
> I think Perl BP is a very good book, and I also use
> K&R style (before
> reading this book, actually), but for example, the
> chapter about OO is ok,
> but, I don't think using inside out object, and
> specially Class::Standard is
> the "best-way".
> 
> So I don't think that there is nothing wrong about
> using BSD coding style,
> the really important thing is that the code doesn't
> have any bug, and the
> style is consistent through the entire book ;-)
> 
> 
> Another thing that would be nice to see in your book
> > is modules that are similar to Data::Dumper such
> as
> > Smart::Comments.  I came across this in the book
> Perl
> > Hacks and thought wow this is pretty nifty and
> > complements Dumper well.
> 
> 
> 
> First mentioned in PBP. Perl Hacks came out later...
> 
> Erm, Data::Dump::Streamer is more something like
> Data::Dumper. YAML also let
> you dumping a la Data::Dumper.
> 
> Smart::Comments main purpose is not to dump data
> structure, it's more like
> on the go debugging... IMHO
> 
> But of curse, it's very useful as well.
> 
> I would like to see on chapter about hooking into
> other languages, mentions
> to XS, Dynaloader, Inline. Also about hooking
> through interface not to other
> languages, I mean, a view from 1000ft to the
> different modules for doing
> remote calls, from RPC to SOAP and Jabber.
> 
> On handling error, could be say that you can even
> have real exceptions
> hierarchies using Exception::Class. Other thing also
> interesting and forgot
> by many is the subroutine arguments validation, from
> normal testing to
> things like Params::Validate and others.
> 
> Perl threads and POE :-)
> 
> Kind Regards,
> 
> Florian
> 
> 


ok understood and yes to further comment on your last
paragraph Florian, Web related programming modules
chapter would be cool, such as AJAX and SOAP. Since
Perl and Java go hand and hand and a lot of companies
want both these skills, is there any possibility a
hook could be explored into Java within this new book?

ciao, 
derek

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com