Hello and welcome :-)
When a method is « public » , it means that it is usable by any other object
in the system.
In Pharo, methods are « public » and instance variables are « protected ».
« protected » means that the instance variable is only usable from inside the
class defining it or
Generically across programming languages...
- a private method can only me invoked by an object of the same class (or
subclass) i.e. it can only be invoked by itself.
- a public method can be invoked from any object.
In Pharo, variables are private and methods are public.
The advantage of
--- Begin Message ---
hello guys
I'm new to programming, I started programming using pharo, I had a question
about pharo's object model. In object model we say, methods are public. What
does "public" mean here?
thanks
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
---
> Objet: Rép : [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)
>
>> I really like the tool as it makes cross-platform-life a lot easier.
>
> Thanks :-)
>
>> I really wish there was a similar tool for the reverse direction, too!
>
> That is interesting. Anyone else interested in such
Guillermo, deleting the VM worked. :)
Newer version of PharoLauncher can update the VM when necessary? I remember
I updated it about two months ago.
On Wed, Nov 14, 2018 at 12:57 PM Guillermo Polito
wrote:
>
> On Wed, Nov 14, 2018 at 3:50 PM Baveco, Hans wrote:
>
>> On windows 7 the 32bits
On Wed, Nov 14, 2018 at 3:50 PM Baveco, Hans wrote:
> On windows 7 the 32bits version opens with an error: “PrimitiveFailed:
> primitive #fileDescriptorType: in File class failed.”
>
> When discarding the error and saving & quitting the image, subsequent
> startups (via the launcher) do not
Hi Hans,
On Wed, 14 Nov 2018 at 15:50, Baveco, Hans wrote:
>
> On windows 7 the 32bits version opens with an error: “PrimitiveFailed:
> primitive #fileDescriptorType: in File class failed.”
>
> When discarding the error and saving & quitting the image, subsequent
> startups (via the launcher)
Do you (does the pharo vm) have full read/write access to its .changes and
.sources file (in the directory where they are stored) ?
> On 14 Nov 2018, at 15:50, Baveco, Hans wrote:
>
> On windows 7 the 32bits version opens with an error: “PrimitiveFailed:
> primitive #fileDescriptorType: in
On windows 7 the 32bits version opens with an error: “PrimitiveFailed:
primitive #fileDescriptorType: in File class failed.”
When discarding the error and saving & quitting the image, subsequent startups
(via the launcher) do not display the gui anymore...
Hans
From: Vitor Medina Cruz
Sent:
Hello,
Thank you Sean :)
>> So is it possible to define such constraints ?
>
> IIUC you could use #onConflict: and be more specific in the block as to
> allow only the specific case you mentioned, but I think the more common
> approach is to use the Metacello API to "lock" NeoJSON to the
Hi Vitor,
On Wed, 14 Nov 2018 at 14:37, Vitor Medina Cruz wrote:
>
> Got instant red crossed welcome window on windows 7 64bits with the Pharo 7
> 64 bits: "Error: Instances of SourceFileArray are not indexable". I will try
> on a windows 10 version later.
Which VM are you using?
Hi Hans,
On Wed, Nov 14, 2018 at 2:56 PM Baveco, Hans wrote:
> Ok, thanks for this crucial information! Would backporting be as simple as
> filing out the class and the single method from Pharo7 and filing in in
> Pharo6.1 ? (probably not)
>
While not completely sure, I think they actually
Ok, thanks for this crucial information! Would backporting be as simple as
filing out the class and the single method from Pharo7 and filing in in
Pharo6.1 ? (probably not)
I could also move y application to Pharo 7, but sofar I haven’t been able to
load Roassal2 in Pharo 7 (32bit). Any
Got instant red crossed welcome window on windows 7 64bits with the Pharo 7
64 bits: "Error: Instances of SourceFileArray are not indexable". I will
try on a windows 10 version later.
32bits version open up ok, will see how it behaves.
regards,
Vitor.
On Wed, Nov 7, 2018 at 6:43 AM Tudor
14 matches
Mail list logo
