Nick Glencross <[EMAIL PROTECTED]> wrote:

> I've now split the code into a library, an example and a test.

Good.

>   * runtime/parrot/include/Digest_MD5.imc (_md5sum and _md5_print calls)
>   * examples/assembly/md5sum.imc
>   * imcc/t/syn/md5.t

> I don't know if the test lives in the most appropriate directory.

Rather not. t/lib or such. Jens?

> Also, I tried using the @MAIN pragma, this seemed to break with JIT
> (I've left it in the example harness, but not the tests). Should I have
> expected this to work? If not, I'll remove it from the example.

Should work, but is broken. Dunno yet why.

> Could I be getting close to having this included with parrot?

Yep. We really should start with some lib directory structure though.

> Cheers,

> Nick

leo

Reply via email to