On 05/12/2013 22:59, Mike Small wrote:
Would it work for you to keep your hash but make the values instead be
references to arrays of references to objects with the attributes you
mention above: address, width, masks, etc.? Are the values in your
current hash objects with such attributes? Is
I use this environment for asic verification. So one kind of test is to
randomize every register with data. But different types of registers have
different valid data definitions. For example, one type of register is 16 bits
wide with the top 5 bits representing an exponent, and the remaining
Original Message
Subject: [tpm] Larry Wall in a crossword puzzle!
Date: Fri, 06 Dec 2013 12:43:10 -0500
From: Henry Baragar henry.bara...@instantiated.ca
To: TPM toronto...@pm.org
Hello everyone,
Checkout clue 65 in the crossword puzzle printed at
On 12/06/2013 11:47 AM, Me wrote:
I use this environment for asic verification. So one kind of test is
to randomize every register with data. But different types of
registers have different valid data definitions. For example, one
type of register is 16 bits wide with the top 5 bits representing
Tuesday December 10, 2013 E51-376 Tim King - Benchmarking Perl6 vs Perl5
* Perl 6's suitability for production. (Your definition may vary.)
* Experiences of the state and stability of Rakudo.
* Benchmarks of my favorite P6 features.
* Lines of P6 code from everyday life.
* Some comparisons of P6
then the code to do stuff is generic across ALL the register types.
Wouldn't I get that with polymorphism?
If every class had randomValidDate()
and each method handled the different
internal data format, don't I get a
generic interface for all register types?
I'm not familiar with this table
On 12/06/2013 09:25 PM, Bill Ricker wrote:
Tuesday December 10, 2013 E51-376 Tim King - Benchmarking Perl6 vs Perl5
* Perl 6's suitability for production. (Your definition may vary.)
* Experiences of the state and stability of Rakudo.
* Benchmarks of my favorite P6 features.
* Lines of P6 code