Saturday, November 30, 2013

Twitter app using perl - Tweet your status - Part 2

Hi All,
The second part will be simple to update your own status using the perl script.
For that initially, you need to go setting tab.


Under the setting tab, change the permission setting for your app to read , write and acess direct message as given below


Friday, November 29, 2013

Twitter app using perl – Part 1


Hi All,

I thought it would be nice quest to create an aap with Step by Step guide.
Here in this series , I will gonna create an app for twitter using Cpan module “Net::Twitter“.


Step 1 .
You need to create an account on dev.twitter.com and need to register your new app.

Step 2.
If you have already finished up with step one , by now you must be having following details for new registered app
Consumer key
Consumer secret
Access token
Access token secret

Tuesday, November 26, 2013

Perl special variable cheat sheet

Hi all,

Again this will be a post for the perl lover.
Recently I was browsing, I  came across the blog of Peteris Krumins blog. The blog has list of interesting article concerning Perl, awk and sed.

One of the article, that attracted my regex mind was his Perl special variable cheat sheet. His 4 page cheat sheet is really easy and collate all the special variable, you may  require play code golf. (I really did not know , Perl has that many special variable)
You can download the cheat sheet here  or from the original link.



Friday, November 15, 2013

Perl vs perl

The following discussion is an expansion on a question and answer which can be found in the perlfaq1 page of Perl's documentation, namely:
What's the difference between "perl" and "Perl"?
Sometimes you'll see "Perl" written, with a capital P, sometimes "perl", sometimes even PERL.
Confused? Not to worry, Israel.pm to the rescue :-)
The rules are actually quite simple:
  • "Perl" should be used when one is writing about the language, for example:
    Perl is a language optimized for scanning arbitrary text files, extracting information from those text files, and printing reports based on that information. It's also a good language for many system management tasks. The language is intended to be practical (easy to use, efficient, complete) rather than beautiful (tiny, elegant, minimal).
  • "perl" should be used when one is writing about the executable which interprets and compiles the Perl code, for example: the perl executable can usually be found at /use/bin/perl on Unix/Linux systems, or on c:\Perl\bin\perl.exe on Windows systems.
  • The above two usage forms are not rigidly adhered to, even in Perl's documentation, but in any case you should never use "PERL".
    "PERL" is a backronym, so unless you are going to use it as a joke, don't. It is way overused and abused, and it is time to put it to rest.
There's a famous saying, attributed to Tom Christiansen, which says that Only perl can parse Perl
We'll leave you now to ponder these words of wisdom...

Wednesday, October 30, 2013

number sequence database for mathlover



Do you have a number sequence that came up your in your mind and think it is a unique in some way , then u have encountered into a discovery of new series of number like like prime number
1,2,3,5,7,11,13,17

The above is the series of the number are divisible by itself.

But before reporting it  and being happy for this accomplished task, do check it on number sequnce database. In integer database ,you can submit your  sequence and validate that is found or yet to be discovered.

Check out . Its is fun.

Thursday, September 19, 2013

runtime error opening '.......'" for reading: -102 (file not found.). on virtual box

Recently I had an issue in regard to the"runtime error opening '.......'" for reading: -102 (file not found.)" on my virtual box . I did the search and could not found any proper solution in a single post..

So Here I am telling the solution that worked for me.


Monday, September 9, 2013

Know Thy Complexities!!!!

Hi there!  This webpage covers the space and time Big-O complexities of common algorithms used in Computer Science.  When preparing for technical interviews in the past, I found myself spending hours crawling the internet putting together the best, average, and worst case complexities for search and sorting algorithms so that I wouldn't be stumped when asked about them.  Over the last few years, I've interviewed at several Silicon Valley startups, and also some bigger companies, like Yahoo, eBay, LinkedIn, and Google, and each time that I prepared for an interview, I thought to msyelf "Why oh why hasn't someone created a nice Big-O cheat sheet?".  So, to save all of you fine folks a ton of time, I went ahead and created one.  Enjoy!
GoodFairPoor