Re: updating hash from perl -> xsub

It may be that there is a monk that recognises your problem domain and therefore understands what your pseudo code and cryptic abreviations mean and can help you. However, if you want a larger number of eyes to look at your problem without glazing I'd seriously consider writing a short test script that demonstrates your problem without obfusicating abreviations and unrunable code. It may help to read I know what I mean. Why don't you?.

DWIM is Perl's answer to Gödel

Comment on Re: updating hash from perl -> xsub

Replies are listed 'Best First'.
Re^2: updating hash from perl -> xsub by gellyfish (Monsignor) on May 21, 2006 at 08:41 UTC
To be fair on the OP these aren't "pseudo code and cryptic abreviations" but XS code and the output from Devel::Peek which would be instantly familiar to anyone who has written XS or been involved with development of the Perl core. Of course there are a smaller number of potential readers who might be able to help with the problem but I am not sure that it could be expressed any differently. /J\	[reply]
Re^3: updating hash from perl -> xsub by GrandFather (Saint) on May 21, 2006 at 10:40 UTC
Fair enough. My first reaction when reading through most of the sample code was: "This isn't Perl, it's C" (there's a reason for that). A heads up that this was in the context of XS would save a little wasted time, both for those of us trying to make sense of what, at first glance, looks like a C programer's first attempts at Perl, and those reading through the replies. True, it's not pseudo code, they are however cryptic abbreviations, and it is indeed true that indicating that the problem deals with XS code would save a few glazed eyes. :) DWIM is Perl's answer to Gödel	[reply]