I'll try my best :). If worse comes to I install Google Perftools locally to solve my immediate need. But ultimately my colleagues and I will need to come up with a workflow for use/installation/recommendation on organisation wide shared systems where commercial profilers are already installed. From our point of view, installing and maintaining Yet Another Profiler, and documenting its use particularly for Rcpp, on top of all our other profiling documentation, is a messy approach.
> From: Dirk Eddelbuettel [mailto:e...@debian.org] > > That would be excellent! Profiling is an important topic, and we have > not covered it in great detail. > > Dirk > > -- > Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com _______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
