Re: [Pharo-dev] Reflecting on data (literal) object syntax

bound to the external interface and does not need to be subclassed. I'm interested how the printing of Values is different to #storeString. Norbert Am 04.07.2017 um 09:05 schrieb Christian Haider <christian.hai...@smalltalked-visuals.com <mailto:christian.hai...@smalltalked-visuals.co

Re: [Pharo-dev] Reflecting on data (literal) object syntax

etreff: Re: [Pharo-dev] Reflecting on data (literal) object syntax Hi Christian, Am 03.07.2017 um 11:06 schrieb Christian Haider <christian.hai...@smalltalked-visuals.com <mailto:christian.hai...@smalltalked-visuals.com> >: I solved this with Values[1] for VW and I am very ha

Re: [Pharo-dev] Reflecting on data (literal) object syntax

Now with Iceberg, if VisualWorks might work with git that would knock > down one barrier and I might have another go. > > On Mon, Jul 3, 2017 at 5:45 PM, Christian Haider > <christian.haider@smalltalked- > visuals.com[mailto:christian.hai...@smalltalked-visuals.com]> wrote:

Re: [Pharo-dev] Reflecting on data (literal) object syntax - porting PDF

k down one barrier and I might have another go. On Mon, Jul 3, 2017 at 5:45 PM, Christian Haider <christian.hai...@smalltalked-visuals.com <mailto:christian.hai...@smalltalked-visuals.com> > wrote: I did Von: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org <

Re: [Pharo-dev] Reflecting on data (literal) object syntax

esting ! Maybe you can release your software with an MIT licence ? Regards, On Mon, Jul 3, 2017 at 10:06 AM, Christian Haider <christian.hai...@smalltalked-visuals.com <mailto:christian.hai...@smalltalked-visuals.com> > wrote: I solved this with Values[1] for VW and I am very ha

Re: [Pharo-dev] Reflecting on data (literal) object syntax

I solved this with Values[1] for VW and I am very happy with it (using it intensively/routinely). Your example would look like: (PointCollection points: (Array with: (Point x: 10 y: 20) with: (Point x: 5 y: 8) )) As you see, it is the same except that

[Pharo-dev] Heise

You made it on Heise News! https://www.heise.de/newsticker/meldung/Programmiersprache-Pharo-6-bekommt-6 4-Bit-Versionen-und-neue-Tools-3737593.html Congrats,

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

Namespaces – please. Best, Christian Von: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Im Auftrag von Henrik Nergaard Gesendet: Mittwoch, 13. Januar 2016 14:24 An: Pharo Development List Betreff: Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI If