in reply to Re^2: PDL undefined reference to pdl_pthread error on install
in thread PDL undefined reference to pdl_pthread error on install

Belatedly...
One of the factors for choosing Perl was that everyone has said how you can easily see what you are doing, until you realise that the people who are saying this are all mainly just using Perl to aid writing their c.
I don't think there are many people who "mainly just (use) Perl to aid writing their c". Speaking as maintainer of PDL, which according to me is the most exaggerated Perl-to-write-C environment that exists, the aim of at least PDL is to enable writing Perl things that run Really Fast. In other words, the Perl in PDL is to enable Perl, just utilising C to do so (just like Perl itself which is written in C).

If you know differently, I'd be highly interested to hear about it.

  • Comment on Re^3: PDL undefined reference to pdl_pthread error on install

Replies are listed 'Best First'.
Re^4: PDL undefined reference to pdl_pthread error on install
by Don Coyote (Hermit) on Jan 31, 2025 at 18:54 UTC

    Perl is one of those different things to different people kind of languages, I believe I was probably just expressing a point of view where i couldn't c the wood for the cc's, not trying to detract from PDL at all, merely trying to understand better what perl is and how to use it.

    I watched a lecture recently and there was a quote that kind of made sense to me regarding this, their view being that perl could be seen as a compiler for compilers. Unfortunately i cannot recall the identity of the speaker.

    I like things working fast so thats great, but i also like understanding how things work, mainly so that im not replicating work uneccessarily.

    One of the main areas im tryng to differentiate from is the assembly/machine code/c/perl/xs relations and pipelines and now of course PDL being thrown into the mix. Im sure once I understand what it is that is going on i'll be more relaxed about what im doing.