http://qs1969.pair.com?node_id=1180099


in reply to Re: Is this a sane/safe way to pass an aref into a C function?
in thread Is this a sane/safe way to pass an aref into a C function?

Thanks syphilis, I never thought about cross-compilation!

This definitely isn't my end result here, but as I said in an earlier reply, I'm kind of just learning C, so that didn't cross my mind.

As I still to this day write my Perl code to compile on as far back of a version as I possibly can (5.8.x minimum), this is a nice piece of feedback, and another avenue of research I have to do as I pick up on C. Learning C is important to me as I have a lot of hardware-interaction software I want to write.

Perlmonks++ for being able to post something only somewhat relative to Perl and getting help for other languages. One thing is for certain... I had an easier time picking up on C pointers than I did originally figuring out Perl references, but while I was learning how to master those (perl refs), I had no programming experience whatsoever. However, this pointer-to-pointer thing (**) is a bit elusive still, so that's another "book learnin'" thing I still have to pick up on ;)

update: Above, I didn't mean learning Perl references was overly difficult (in fact, they're not... they're quite logical). The comparison is unfair; I hadn't done but a lick of coding when I had to figure out refs in Perl, but once I grasped them, references/pointers/whatever-you-want-to-call-them became immediately understandable. So really, learning Perl refs allowed me to understand the concept behind *any* languages that has the concept of the sort.