Higher Order Perl
I am in love with the book Higher-Order Perl, especially the technique in the Chapter 2: Dispatch Tables.
I am in love with the book Higher-Order Perl, especially the technique in the Chapter 2: Dispatch Tables.
Today morning I came across this piece of writing - Does GPL still matter?. The whole article is based on a few anecdotes from CEOs and marketing droids. They have gotten quite a few points wrong in the article.
GPL is a developer friendly license. The basic premise of the GPL is that the user should not subtract from the freedom he gets when redistributing software. GPL is not restrictive. It merely insists that whoever takes from the common pool must contribute back to the pool.
I would like to point to these 2 articles in support of GPL -
I attended the Hackers and Founders meetup yesterday. It was a high energy meetup and I liked it. When I walked in, I was already 2 hours late but there were still quite a few people around. I walked in, took a name tag and tried to "merge in". Merging was easy - the folks were friendly and did not mind if you joined the discussion.
Some observations
I am using a Mac now, and this blog post is brought to you by the same php and lisp scripts that I was using on my linux box. Cheers! ![]()
Have you read the man malloc page recently? Did you notice this section there
Recent versions of Linux libc (later than 5.4.23) and GNU libc (2.x) include a malloc implementation which is tunable via environment variables. When MALLOC_CHECK_ is set, a special (less efficient) implementation is used which is designed to be tolerant against simple errors, such as double calls of free() with the same argument, or overruns of a single byte (off-by-one bugs). Not all such errors can be protected against, however, and memory leaks can result. If MALLOC_CHECK_ is set to 0, any detected heap corruption is silently ignored; if set to 1, a diagnostic is printed on stderr; if set to 2, abort() is called immediately. This can be useful because otherwise a crash may happen much later, and the true cause for the problem is then very hard to track down.
So, you can do export MALLOC_CHECK_=1 and malloc will
print debugging messages to the stderr.
I have created a emacs major mode, called lunatech-journal, that I use for blogging. It is a derived mode from muse-mode, an excellent mode for writing and publishing.
Currently, it has following functions defined
lunatech-journal-skeleton - loads a skeleton for blogginglunatech-journal-show-hints - shows a buffer with questions to help me blog about my daylunatech-journal-make-html - creates a html file from the muse-modelunatech-journal-preview - allows me to preview my journal in the browserI use a php script to post the blog entry to the website. To use it, I have the following in my .emacs file
(defun journal ()
(interactive)
(find-file "~/blog/journal.muse")
)
(require 'lunatech-journal)
(add-to-list 'auto-mode-alist '("journal\\.muse\\'" . lunatech-journal-mode))
When I feel the need to blog, I do M-x journal, I get dropped into my
journal file and I can blog.
Links:
testing, testing - 1, 2, 3
I should now be able to set the categories of my post.
This post is brought to you by emacs, php and lots of cups of tea.
Page 2 of 5, totaling 33 entries