Me: oi, there's like a few dozen modules I need to rebuild that have changed their maintainers, so their CPAN paths all changed, now I need to update them all, sounds like a bit of busywork, 'innit?
MetaCPAN: don't fret, we have this nifty feature where you use the /modules/by-module/X/X-Y
paths, and those won't change!
Me: OK mate!
... time passes ...
... I need to rebuild the packages again.
Me: MetaCPAN, mate, do you know why am I getting 404 pages instead of tarballs under all /modules/by-module/...
links? Now I have to change them all back to author-based ones! Sounds like busywork again, 'innit?
MetaCPAN: LOL LMAO
submitted by /u/WesolyKubeczek
[link] [comments]
[link] [comments]
Day 12: 3D visualization of scalp electrode sites can be done with Perl
3D visualization of scalp electrode sites for EEGpdl.perl.org
Is there a way to directly include a variable declared in a dumped config file in one of my scripts? The structure of the file is below:
{ my $variable = { “key1” => { “key2” => { “key3” => “value1”, }, }, }; }
1;
As you can see, the variable declares a deeply nested hash_ref which I don’t want to have to parse manually. I also don’t have any control over the dumped variable file, the design flow I am working in dumps that format and it would both be cumbersome to try and get the script owner to modify the output to use our instead of my and this could anyways possibly effect currently existing downstream flows that depend on this specific format. As for why we didn’t use a yml in the first place, no idea lol
For reference, I need to take a list of keys from within the hash and iterate over each element
submitted by /u/Its-goodtobetheking
[link] [comments]