[Pharo-dev] DigitalSignatureAlgorithm depends on Sound

Hi I discovered that UUIDGenerator and DigitalSignatureAlgorithm used in some encrypting algo are dependent of Sound. BaseSoundSystem>>:randomBitsFromSoundInput: bitCount "Answer a positive integer with the given number of random bits of 'noise' from a sound input source. Typically, on

Re: [Pharo-dev] Discard option while editing code seems to be broken or strange

Yes I have this bug times to times but no mean to reproduce it. On 3 août 2013, at 21:27, Stéphane Ducasse wrote: > When I modify a method and click on somewhere else I get a pop up and > pressing discard does not work but pops up another. > Now I'm trying to reproduce the problem to describe i

Re: [Pharo-dev] New version of PharoSound

May I ask for a small favor ? That you guys each time you refer to a pharo library you also link its project page that hopefully contains also its docs. So we can all follow you easily. I know google is my friend but I do think its more convenient and a better motivation for people to try new l

[Pharo-dev] New version of PharoSound

Hi I merged Jannik clean and I commited a new version of the configuration. Now it works on Pharo 20 and also on Pharo 30 And I will produce a new System-Sound for the kernel based on Pavel work and I will produce a new configuration. Stef

Re: [Pharo-dev] Smalltalk = strongly typed

Hi Ben, Even if you adopt a type system or definition as part of Smalltalk, it is not coherent nor intuitive with the system usage. Types are not identifiable in Smalltalk, they belong to other systems semantics (both formal and informal) and probably scientific corpus. Because of that, you ar

[Pharo-dev] Discard option while editing code seems to be broken or strange

When I modify a method and click on somewhere else I get a pop up and pressing discard does not work but pops up another. Now I'm trying to reproduce the problem to describe it clearly and I cannot anymore but I'm sure I did get this strange behavior. Stef

Re: [Pharo-dev] Smalltalk = strongly typed

btc wrote > btc@ > wrote: > > Kilon, I agree with most of you writeup, except that I think Smalltalk > has types - except the types are not associated with variables, rather > they are associated with objects. This aligns with Igor's comment "in > smalltalk, assignment is not copying value,

[Pharo-dev] SimpleMIDIPort midiIsSupported returns the first time false and after all the time true :)

Strange May be the logic in the primitive is strange. midiIsSupported "Answer true if this platform supports MIDI." ^ self primPortCount > 0 primPortCount "Answer the number of MIDI ports supported by this platform, or zero if this primitive is not implemented."

Re: [Pharo-dev] is the apply in the merge tool working?

I checked the code and it does not apply immediately the changes so it looks like it i redundant with keep current or keep incoming. Stef On Aug 3, 2013, at 7:09 PM, Stéphane Ducasse wrote: > Because when I merge and I click on apply the change is not applied in the > image (when I do not acc

Re: [Pharo-dev] Smalltalk = strongly typed

b...@openinworld.com wrote: greetings all, I'm in the final weeks of writing up my Masters dissertation and seeking some scholarly references to Smalltalk being "Strongly Typed." I my review of Smalltalk I was surprised to find that [1] describes Smalltalk as Strongly Typed, since Smalltalk

[Pharo-dev] Still broken Date comparaison in 2.0?

Instances value from stacking GrowlMorphs: TimeStamp now -> 4 August 2013 1:18:30 am vanishTime -> 4 August 2013 12:51:51.62 am TimeStamp now < vanishTime ->true Inspectors: Hilaire -- View this message in context: http://fo

[Pharo-dev] is the apply in the merge tool working?

Because when I merge and I click on apply the change is not applied in the image (when I do not accept the button in the merge tool)? Stef

[Pharo-dev] cleaning AppRegistry and Sound/SoundService...

Hi guys I wonder what we can do about AppRegistry I imagine that we can remove MailSender. I'm going over the code on the image as well as http://code.google.com/p/pharo/issues/detail?id=6996 and pavel changes. Any feedback is welcome. Stef

Re: [Pharo-dev] Smalltalk = strongly typed

The term "strongly typed" is ambiguos and this thread is the living proof of that. In the introduction of http://lucacardelli.name/Papers/OnUnderstanding.A4.pdf Luca Cardelli talks about untyped universes and later about Smalltalk. For me Smalltalk is a dynamically typed language with implicit ty

Re: [Pharo-dev] Smalltalk = strongly typed

BTW, I especially like the idea that Smalltalk is Multityped, as an object can respond to several protocols/interfaces/type specs. So true! Quoting "Carla F. Griggio" : > Well, I've always defined a type as the a set of values and the operations > you can do with them. For example, the set o

Re: [Pharo-dev] Smalltalk = strongly typed

I fully agree with you. Just a detail. "strongly typed" or "weakly typed" is not ambiguous. Weakly typed means that the system can not guarantee that the types are known and behavior is consistent with them. The main example is C, where a pointer can point to anything, and often there is no ty

Re: [Pharo-dev] Smalltalk = strongly typed

" Smalltalk has types: a set of objects and the messages they understand" Nope thats not what a type is. A type is a category of data. Its that simple. Your set of objects and the messages they understand can do thousands of things. Emulating types is one of those things. Also what happens in

Re: [Pharo-dev] Large images reasons [WAS] Re: [Pharo-users] Pharo 2.0 with Seaside + DBXTalk + GlorpDBX + Magritte 3 + TWBS is getting slower and slower

On Aug 3, 2013, at 2:13 AM, Eliot Miranda wrote: > Hi Marcus, > > On Thu, Aug 1, 2013 at 12:33 AM, Marcus Denker wrote: >> >> On Aug 1, 2013, at 8:56 AM, Stéphane Ducasse >> wrote: >> >>> since years marcus is telling that MC storing ancestor information is >>> doomed but we do not have s