Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Bernhard (4508)

https://www.xing ... hard_Schmalhofer

A freelance software engineer with experience in webapplications, databases and bioinformatics.

A contributor to Parrot and the person behind Pipp.

A physicist who worked with third sound in Helium-III and CCD X-ray detectors.

barney on
github: []
LinkedIn: []
XING: []

Journal of Bernhard (4508)

Tuesday October 26, 2004
03:03 PM

'make distclean' is not my friend

[ #21526 ]

Over the weekend I have been looking into the Perl Data Language, PDL. Nice! There is ample support for visualisation and the Gnu Scientific Library is there too.

However for the next picture drawing, or number crunching task, I would like to finally get started on R. I think that with R it is much easier to do statistics. Also there seem to exist some bioinformatics packages for R.

Back to PDL: The basic data structure of PDL is a multidimensional array, usually called 'piddle'. It would be a nice challenge to bring piddles to Parrot as PMCs. Loooking at the docs and the C header files, it shouldn't be too hard. One should be able to load the shared libs that are already generated for Perl5.

For my work on bringing 'libsyck' to Parrot, there is good and bad news. The good news is that synchronous callbacks are now in Parrot. 'libsyck' really needs synchrounous callbacks, as it passes weak references back to the Parrot interpreter.

The other good news is, that Stéphane Payrard started to work on a multifacetted PMC, 'siva'. The 'siva' PMC seems to be ideal for building up a parse tree of a YAML document.

The bad new is, that a couple of weeks ago I did a 'make distclean' on my working copy of the Parrot sources. This sent all my new libsyck files into Nirvana. Luckily I'm doing this for fun.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.