> On 8 Mar 2018, at 17:58, Eliot Miranda wrote:
>
> Hi Stef,
>
> following on from Sean, (+1000 for using ordinary quotes)
>
> ’string’ collection of characters => ’string’ sequence of characters
> $a, Character space Two ways to create characters => $a, Character
Hi Stef,
following on from Sean, (+1000 for using ordinary quotes)
’string’ collection of characters => ’string’ sequence of characters
$a, Character space Two ways to create characters => $a, Character
space two ways to denote characters (or two ways to write characters; all
other explanations
stepharo wrote
> new cheatsheet for Pharo syntax.
> Any feedback is welcome
Looks great! (and surprise, it covers much more than just syntax).
A few observations:
1. The code examples have smart quotes. This can create confusion. If it's
not too much trouble, copy/pasteable-into-Pharo single
normally yes.
On Thu, Mar 8, 2018 at 10:48 AM, H. Hirzel wrote:
> Hello
>
> Is the cheat sheet
> http://files.pharo.org/media/pharoCheatSheet.pdf
>
> up to date for Pharo 6.1 and Pharo 7?
>
> In particular - the references to the main web sites, are they still OK?
>
>
>
Hello
Is the cheat sheet
http://files.pharo.org/media/pharoCheatSheet.pdf
up to date for Pharo 6.1 and Pharo 7?
In particular - the references to the main web sites, are they still OK?
MainWebSites
- Codehosting http://smalltalkhub.com
- Questions http://discord.gg/Sj2rhxn
- Blog
Le 12/4/16 13:39, Eliot Miranda a écrit :
#(4 3 1) at: 3 put: 6 => either
#(4 3 1) copy at: 3 put: 6
or
{ 4. 3. 1} at: 3 put: 6
Sooner or later literals are going to be immutable and then #(4 3 1) at: 3 put:
6 will raise an exception.
eager to have that :)
I used the copy.
"a debugger, a workspace and object inspectors" => "compiler, debugger,
workspace, object inspectors"
and maybe drop "object"
then it flows into "and much, much more". That the compiler is implemented in
Smalltalk is v important, IMO.
_,,,^..^,,,_ (phone)
> On Apr 11, 2016, at 11:58 PM,
"There is no type declaration, ..." => "There are no type declarations, ..."
_,,,^..^,,,_ (phone)
> On Apr 11, 2016, at 11:58 PM, stepharo wrote:
>
> new syntaxsheet
>
>
>
#(4 3 1) at: 3 put: 6 => either
#(4 3 1) copy at: 3 put: 6
or
{ 4. 3. 1} at: 3 put: 6
Sooner or later literals are going to be immutable and then #(4 3 1) at: 3 put:
6 will raise an exception.
_,,,^..^,,,_ (phone)
> On Apr 11, 2016, at 11:58 PM, stepharo wrote:
>
> new
In the "common constructs" conditionals and iterations tables, the Java appears
on the left and the Smalltalk on the right. In other tables the Smalltalk
occurs on the left and the explanation appears on the right. Hence, in the
conditionals and iterations tables, put the Java on the right.
Hi Stef,
"boolean objects" => "the boolean objects"
"the receiver, in the superclass context" => "ditto, for accessing overridden
inherited methods"
"the current invocation on the call stack" => "the current method or block
activation"
_,,,^..^,,,_ (phone)
> On Apr 11, 2016, at 11:58 PM,
I agree that enumeration is more useful but it wouldn't be bad to have
something in there to indicate the 1-index nature, such as
*'abcd' at: 2* will result in $b
That's all I was suggesting.
Actually, having some cheat sheet on basic enumeration wouldn't be bad as
that is a real strength of
On 09/04/2016 10:59,
serge.stinckw...@gmail.com wrote:
Yes you are right. We have 2 students (3rd Year at University) here that have
been exposed only to C or Java and they are totally index-intoxicated ... They
can't reason on collections. Difficult for them to change their habits.
Sent from
Le 9/4/16 10:04, philippe.b...@highoctane.be a écrit :
On Apr 9, 2016 9:54 AM, "olivier auverlot" > wrote:
>
> I think that it could be interesting to use it also on a simple
HTML page for the Pharo web site. This document
Yes I should/may update it
Le 8/4/16 22:03, Cyril Ferlicot Delbecque a écrit :
On 08/04/2016 21:56, stepharo wrote:
new cheatsheet for Pharo syntax.
Any feedback is welcome
Hi,
The screen seems to be from Pharo 1 no?
Stef
On Sat, Apr 9, 2016 at 3:52 PM, olivier auverlot
wrote:
> I think that it could be interesting to use it also on a simple HTML page
> for the Pharo web site. This document can be put in the main menu
> ("Beginners" ?) just before "Documentation".
>
> It's really cool
On Sat, Apr 9, 2016 at 3:56 AM, stepharo wrote:
> new cheatsheet for Pharo syntax.
> Any feedback is welcome
So I really went to town and picked the eyes out of it...
> #(abc 123)
> literal array with the symbol #abc and the number 123
This one surprised me. I had to test it
Yes you are right. We have 2 students (3rd Year at University) here that have
been exposed only to C or Java and they are totally index-intoxicated ... They
can't reason on collections. Difficult for them to change their habits.
Sent from my iPhone
> On 9 avr. 2016, at 11:51, Stephan Eggermont
On 09-04-16 10:55, Cyril Ferlicot D. wrote:
I use Pharo since 1 year now and I had to use indexes only 3-4 times.
Probably on day 1 and 2 :)
The problem is that people new to Smalltalk have a background.
If they have programming experience, it is likely with a language where
indexes are
@cyril +1
Le 9 avr. 2016 10:56 AM, "Cyril Ferlicot D." a
écrit :
> Le 08/04/2016 22:08, J.F. Rick a écrit :
> > It looks good. I might mention that most data structures are 1 indexed
> > as most other languages tend to be 0 indexed and that throws people new
> > to the
Le 08/04/2016 22:08, J.F. Rick a écrit :
> It looks good. I might mention that most data structures are 1 indexed
> as most other languages tend to be 0 indexed and that throws people new
> to the language.
>
I use Pharo since 1 year now and I had to use indexes only 3-4 times. I
think it is
On Apr 9, 2016 9:54 AM, "olivier auverlot"
wrote:
>
> I think that it could be interesting to use it also on a simple HTML
page for the Pharo web site. This document can be put in the main menu
("Beginners" ?) just before "Documentation".
>
> It's really cool to have
I think that it could be interesting to use it also on a simple HTML page
for the Pharo web site. This document can be put in the main menu
("Beginners" ?) just before "Documentation".
It's really cool to have a synthesis document for the newcomers.
2016-04-09 8:09 GMT+02:00 Ben Coman
On Apr 9, 2016 8:11 AM, "Ben Coman" wrote:
>
> On Sat, Apr 9, 2016 at 6:16 AM, Damien Pollet
wrote:
> > On 8 April 2016 at 22:57, Sven Van Caekenberghe wrote:
> >>
> >> Since we are simpler and more logical, a cheat sheet should not
On Sat, Apr 9, 2016 at 6:16 AM, Damien Pollet wrote:
> On 8 April 2016 at 22:57, Sven Van Caekenberghe wrote:
>>
>> Since we are simpler and more logical, a cheat sheet should not confuse
>> people by describing what we are not.
>
>
> I beg to disagree.
On 8 April 2016 at 22:57, Sven Van Caekenberghe wrote:
> Since we are simpler and more logical, a cheat sheet should not confuse
> people by describing what we are not.
I beg to disagree. "Simpler and more logical" is just your biased point of
view; fact is, zero-based indexing
> On 08 Apr 2016, at 22:08, J.F. Rick wrote:
>
> It looks good. I might mention that most data structures are 1 indexed as
> most other languages tend to be 0 indexed and that throws people new to the
> language.
Actually the others are wrong ;-)
Seriously, in Mathematics 1
Thanks great.
As we are looking language cheatsheet, a few minutes ago, I was reading
an old news[1] about OCaml[2], here its cheatsheet[3]. It is said to be
a great language, supported by INRIA as well, with strong type. But
Pharo makes me fell more comfortable when complexity need to be
It looks good. I might mention that most data structures are 1 indexed as
most other languages tend to be 0 indexed and that throws people new to the
language.
On Fri, Apr 8, 2016 at 3:58 PM stepharo wrote:
> new cheatsheet for Pharo syntax.
> Any feedback is welcome
>
> Stef
29 matches
Mail list logo