[Pharo-project] ThirtyTwoBitRegister methods removed

Mariano Martinez Peck marianopeck at gmail.com
Tue May 19 15:03:34 CEST 2009


On Tue, May 19, 2009 at 6:46 AM, Nicolas Cellier <
nicolas.cellier.aka.nice at gmail.com> wrote:

> To me, this raises a more general question.
> How can we trace a particular change in Pharo?
> Why when and where this change did occur? I know all is in the
> Monticello repository, but is there a quick and convenient way to
> answer such a question? I mean avoiding a manual scan of each and
> every Monticello version...
>
> Or is it logged in the ChangeSet? In this case, what hidden menu or
> code snippet will help tracking the change?
>
> Or should we use the issue tracker? Ideally, the reason for every
> change should be logged here. And every Monticello uploaded should
> refer to an issue. Even if this were strictly applied, not sure that
> is the way to retrieve information at such a detailed level.
>
> If none of these tools can provide an easy answer, then yes, requests
> on mailing lists, IRC, or internet search can provide a much efficient
> answer. But that's the signature a tool is lacking.
>

I am agree. Actually, I thought to add in my email a generic question of
that because I faced this problem several times and I didn't know what to
do.


> I wish Mariano gets an answer, but an answer on the method would be
> more profitable to every one.


No problem. Perhaps someone knows haha.


>
>
> Cheers
>
> Nicolas
>
> 2009/5/19 Mariano Martinez Peck <marianopeck at gmail.com>:
> > Hi folks. I noticed that this two methods were removed from
> > ThirtyTwoBitRegister:
> >
> > asByteArray
> >        ^ ByteArray with: (low bitAnd: 16rFF) with: (low bitShift: -8)
> with:
> > (hi bitAnd: 16rFF) with: (hi bitShift: -8)
> >
> >
> >
> > reverseLoadFrom: aByteArray at: index
> >          "Load my 32-bit value from the four bytes of the given
> > ByteArraystarting at the given index. Consider the first byte to contain
> the
> > mostsignificant bits of the word (i.e., use big-endian byte ordering)."
> >
> >          hi := ((aByteArray at: index + 3) bitShift: 8) + ( aByteArray
> at:
> > index + 2).
> >          low := ((aByteArray at: index + 1) bitShift: 8) + ( aByteArray
> at:
> > index).
> >
> >
> >
> > I need them for Glorp. I looked but I didn't found a similar message for
> > them. I don't think adding them as an extension is a good solution here
> > since this seems to be very "internal". is there a reason of the
> removing?
> > If not, could them be added again? If there are reason, which should be
> the
> > best approach to fix this in mi case?
> >
> > I have no problem in commit them if you want.
> >
> > Thanks!
> >
> > Mariano
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Pharo-project mailing list
> > Pharo-project at lists.gforge.inria.fr
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20090519/a57fea85/attachment.htm>


More information about the Pharo-project mailing list