Re: [Pharo-users] Pharo-users Question about the symbols

On Friday, 8 April 2016, Valentin Ryckewaert wrote: > Hello everyone, > > i'm learning Pharo and i'm having difficulties to understand the symbols, > what are they? How are they different of the ByteString ? Why are they > usefull ? > Why should I put #string where I can put 'string' ? > Hi, As

Re: [Pharo-users] Pharo-users Question about the symbols

And symbols are immutable Brad Sent from my iPad > On Apr 7, 2016, at 9:41 PM, Markus Stumptner wrote: > > As a result, internal names (e.g., method names) are usually symbols. Strings > are normally used for string manipulation, symbols for unambiguous (but > humanly readable!) internal r

Re: [Pharo-users] Pharo-users Question about the symbols

As a result, internal names (e.g., method names) are usually symbols. Strings are normally used for string manipulation, symbols for unambiguous (but humanly readable!) internal reference (vulgo 'naming'). Markus On 08/04/16 10:53, Ben Coman wrote: A symbol is like a string, except that all

Re: [Pharo-users] Pharo-users Question about the symbols

A symbol is like a string, except that all symbols with the same value are in fact the same object; that is, every #hello symbol is the exact same object as every other #hello symbol. See "identically equal" section here... http://sdmeta.gforge.inria.fr/FreeBooks/ByExample/08%20-%20Chapter%206%20-

[Pharo-users] Pharo-users Question about the symbols

Hello everyone, i'm learning Pharo and i'm having difficulties to understand the symbols, what are they? How are they different of the ByteString ? Why are they usefull ? Why should I put #string where I can put 'string' ? Thanks in advance for your answer. Valentin Ryckewaert

Re: [Pharo-users] FFI return by reference

I think in that case you need to pass an instance of FFIExternalValueHolder. On 7 April 2016 at 17:42, Thibault Raffaillac wrote: > Hi again, > > Does anyone know what is the state of return by reference in FFI? > Example: > glGetAttribute: attr into: value > errorCode> > ^ self

[Pharo-users] FFI return by reference

Hi again, Does anyone know what is the state of return by reference in FFI? Example: glGetAttribute: attr into: value ^ self nbCall: #( int SDL_GL_GetAttribute(SDL_GLattr attr, int *value) ) On my image (50666) it does nothing on value yet (if nil, remains nil, if SmallInteger 0

[Pharo-users] Passing nil with FFI

Hi, I am having trouble passing nil to a function with FFI (i.e. NULL, i.e. 0). For example: SDL2 glCreateContext: nil. The function expects a subclass of FFIExternalObject, so calls instVarAt: 1 but nil has no such field! Am I missing something? (like a special nil instance of FFIExternalObject)

Re: [Pharo-users] Pharo-users Digest, Vol 36, Issue 12

Hi Torsten, Thanks fro you reply. I have try to deploy some test app and it work. Best Regards 2016-04-06 18:00 GMT+02:00 : > Send Pharo-users mailing list submissions to > pharo-users@lists.pharo.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.p

Re: [Pharo-users] Installation on Ubuntu 15.10 (64 bits)

On 07-04-16 11:34, Marion Noirbent wrote: Hi, I have installed Pharo on Ubuntu 15.10 (64 bits) with help of another user who ask me to report the troubles we have encountered. Thank you for the feedback. Stephan

[Pharo-users] Installation on Ubuntu 15.10 (64 bits)

Hi, I have installed Pharo on Ubuntu 15.10 (64 bits) with help of another user who ask me to report the troubles we have encountered. By following the instruction on the page http://pharo.org/gnu-linux-installation (and make "sudo apt-get install pharo-vm-core" then "sudo apt-get install pharo-la

Re: [Pharo-users] [ANN] Pomodoro 1.6 for Pharo 5 + video

On 07-04-16 00:53, Torsten Bergmann wrote: I did a new pass on the Pomodoro timer for Pharo 5: Nice. Stephan