Perl 6 - the future is here, just unevenly distributed

IRC log for #pdl, 2013-11-04

| Channels | #pdl index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:34 sivoais want to throw out an idea that I've to experiment with
01:35 sivoais So, I noticed that in my workflow I keep on iterating over small changes to an algorithm and then run the calculations over and over again
01:35 sivoais there may be something to memoizing lots of those calculations between runs
01:36 sivoais and I came across this paper <http://academic.odysci.com/article/1010113015034564/using-automatic-persistent-memoization-to-facilitate-data-analysis-scripting> that does that for Python
01:37 sivoais more info: <http://www.pgbovine.net/incpy.html>, code: <https://github.com/pgbovine/IncPy/>
01:39 sivoais maybe someone with more Perl internals knowledge could see what it would take to do that with PDL? ;-)
01:46 sivoais made a quest for it for others to take up / comment :-) <http://questhub.io/realm/perl/quest/5276fbd99f567ad86f00007c>
02:36 pdurbin interesting
07:16 drrho joined #pdl
08:12 drrho joined #pdl
17:22 _vicash_ joined #pdl
18:07 gtodd can I save the pdl2 shell history interactively with a command?  Devel::REPL uses ":dump filename.txt "
18:09 gtodd I can see my history but it doesn't seem to get saved reliably when the shell/repl crashes ... I'd like to save it as a file before attempting risky stuff :)
18:13 gtodd Im running in a shells using vim when I need to edit ... from pdl2 prompt  I can type "# vim "  but can't figure out how to read the pdl2 history buffer into vim
18:16 sivoais gtodd: pdl2 is a Devel::REPL. All you need to do is make sure you load the DumpHistory plugin
18:17 sivoais so in your .perldlrc,  put
18:17 gtodd ok I'll see if that works :)
18:17 sivoais $_REPL->load_plugin('DumpHistory') if $_REPL;
18:17 sivoais in mine, I just load everything from my repl.rc <https://github.com/zmughal/dotfiles/blob/master/pdl/.perldlrc>
18:18 gtodd excellent!
18:18 gtodd thanks
18:18 gtodd is using perldl pdl  not recommended  pdl2 is the wave of the future?  I see a lot of examples for pdl instead of pdl2 ... are they mostly compatible
18:18 gtodd ?
18:20 gtodd I like and am getting used to re.pl (Devel::REPL) so I figure pdl2 is the best way for me to learn in a REPL setting
18:25 sivoais I'm not sure about that. For learning, they shouldn't be that different. pdl seems to have a faster startup than pdl2, but that's not really an issue for REPLs
18:26 gtodd perfect ...now I can :dump omfg  .... then #xterm -e vim omfg ... then type do omfg to run it :)
18:28 gtodd wwoudl be nice if :dump  could take an arg to dump only the last 20 lines of input or whatever
18:28 gtodd perhaps I can figure that out ... cheers
18:32 gtodd sigh another core dump from Slices.so  .... pdl_writebackdata_affineinternal () ... I wonder if it is my compiler ...
18:32 * gtodd rebuilds PDL
18:33 gtodd I'm pretty sure this time I didn't don anything obviously wrong
19:26 drrho joined #pdl
19:47 drrho joined #pdl
20:49 chm joined #pdl
20:49 chm gtodd : The plan is for perldl and pdl2 to merge into a single pdl shell.
20:50 chm Right now, pdl2 has Devel::REPL as its base which gives some nice features.
20:50 chm It may make sense to base the eventual pdl shell on a lightweight alternative since Moose can take a while to load.
20:51 chm Regarding saving history on crash (it should work if the exit handler is called).  It doesn't work for OOM death.
20:51 chm The best solution would be to update the history file *before* any operations rather than after.
20:52 gtodd yeah that's what I'm doing .... since I still get core dumps :-\
20:52 gtodd tried recompiling etc.
20:52 chm gtodd : as always, PDL support is provided through the perldl list and the pdl-porters for porting issues....  Good luck.
20:52 gtodd can't get the same error to do anything on older pdl

| Channels | #pdl index | Today | | Search | Google Search | Plain-Text | summary