Hi Stef: On 16 Jun 2013, at 20:43, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I am not aware of a blog post or similar things.
it is coming :) see the attachment.
Just a general remark: I am not sure what Camillo's opinion is, but he had a substantial part in SMark, and if you need to mention names, he should certainly be included.
The benchmark SMarkSuite has also a comment, which gives minimal information of how to use it. Note that I use SMark mostly from the command line. So, it only has a limited set of convenience methods. Most of the time, I use `SMarkHarness run:` as in the example below.
what do you think about initializing the runner of a suite to the be the default one? This way we could do
SmarkLoops new runBenchmark: #benchArrayAccess.
I think you would rather want something like: SMarkSuite class >> #runOnly: aSymbol "aSymbol should refer to a benchmark method. Example: SMarkLoops runOnly: #benchFloatLoop " ^ self defaultRunner execute: (self new runOnly: aSymbol)
What is the <omniUnenforced>? "Hint for the OMOP that it is part of the meta infrastructure" I kind of get that this is a kind of annotation for your phd thesis. Yes. It is a hint for the VM or bytecode transformation that this methods does not need to be subject to the metaobject protocol.
Since it does not really hurt, I did not spend the effort to keep it out of SMark. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525