Just forget this topic. These methods actually are needed by the Cryptography package. Glorp port to Squeak only can be used with Postgres. So, I was doing the test with the native postgres driver. But, if you have configured your postgres database with MD5 (as I have), the package Cryptography is needed. I will configure my postgres without md5. When someone has time and do a port of Cryptography I can go on with this.

Sorry for the noise.

Mariano

On Thu, May 21, 2009 at 2:19 PM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:

On May 21, 2009, at 3:10 PM, Mariano Martinez Peck wrote:

>
>
> On Thu, May 21, 2009 at 6:51 AM, St�phane Ducasse <stephane.ducasse@inria.fr
> > wrote:
> If you need them for glorp copy them from Squeak and publish a new
> package version working for Glorp in PharoInbox
> I will push it in pharo
>
> Ok, I will do that. I am trying to see how the fax the license signed.
>
> However, it is not that I NEED it for Glorp. I mean, I can put it in
> Glorp as an method extension with *Glorp and will work. But for me,
> these two methods are ok to be in Pharo.

sounds like so push them

>
>
> Cheers,
>
> Mariano
>
>
> On May 21, 2009, at 3:07 AM, Mariano Martinez Peck wrote:
>
> > I searched in Monticello for the package System-Digital Signatures
> > and in the Pharo repository I only see two commits and even in the
> > first one, these two methods are not there. But, they are in Squeak.
> > So, know I guess where this commit should be? where I can search ?
> >
> > Thanks!
> >
> > Mariano
> >
> > On Mon, May 18, 2009 at 9:27 PM, Mariano Martinez Peck <marianopeck@gmail.com
> > > wrote:
> > 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@lists.gforge.inria.fr
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project