- Pharo-users - lists.pharo.org

Pharo on a Netbook running TinyCore Linux

by tbrunz

This is cool... After I booted TinyCore Linux[1] on my 10-year-old netbook[2], I decided to see if it could run Pharo... It does! Details: [1] http://tinycorelinux.net/ - TinyCore Linux "CorePlus", 32-bit, version 11.1. - Booted from a YUMI multiboot thumbdrive. - Installed 'curl', 'bash', Firefox (to access 'pharo.org' site for download info). [2] https://www.notebookcheck.net/Review-Acer-Aspire-One-D255-Netbook-N550.4015… - Acer D255 "AspireONE" netbook (Sept, 2010). - 2 GB RAM (single DIMM). - 250 GB SSD (not being used; TinyCore running 100% in RAM). The Proof: <http://forum.world.st/file/t372161/Pharo8-32_TinyCore_AcerD255_2020-0907.jpg> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 8, 2020

[Ann] Workshop (3rd session) IndieWeb with pocket infrastructures

by Offray Vladimir Luna CÃ¡rdenas

Hi, This is a short annoucement about our workshops related IndieWeb with pocket infrastructures. Our third session would be this Saturday 12 Sept, from 15:15 to 19:15 (GMT-5). You can find more information in [1] and the documentation in [2]. Following a "local first" approach, the documention and workshops will be happening in Spanish but the interactive notebooks and code will be written in English [3][3a][4][5]. [1] https://is.gd/dataroda50 [2] https://mutabit.com/repos.fossil/indieweb/ [3] https://mutabit.com/repos.fossil/brea/ [3a] https://code.tupale.co/Offray/Brea [4] https://code.tupale.co/Offray/Grafoscopio [5] https://code.tupale.co/Offray/GrafoscopioUtils Cheers, Offray

Sept. 7, 2020

Re: [Pharo-users] Can it do this way ?

by Steffen MÃ¤rcker

Now having a Workspace at hand, I fixed some minor typos: IsbnVarifier>>isSyntacticIsbn: aString | nonGrouped dashes spaces grouped | nonGrouped := '\d{9}[0-9X]' asRegex. "groups separated by either dashes or spaces" dashes := '\d{1,7}-\d{1,7}-\d{1,7}-[0-9X]'. spaces := '\d{1,7} \d{1,7} \d{1,7} [0-9X]'. grouped := (dashes , '|' , spaces) asRegex. ^(aString matchesRegex: nonGrouped) or: [(aString matchesRegex: grouped) and: [aString size = (10 + 3)]] Best, Steffen Am .09.2020, 19:01 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: > Hi, > > after reading the link and some additional sources, it turns out that a > valid ISBN-10 has either no separators or four blocks separated by either > dashes or spaces: > Group-Publisher-Title-CheckDigit > > Assuming Regex11 (and that I made no mistake), the following should do > the > trick: > > IsbnVarifier>>isSyntacticIsbn: aString > "no groups" > noGrouped := '\d{9}[0-9X]' asRegex. > "groups separated by either dashes or spaces" > dashes := '\d{1,7}-\d{1,7}-\d{1,7}-[0-9X]' > spaces := '\d{1,7} \d{1,7} \d{1,7} [0-9X]' > grouped := (dashed , '|' , spaces) asRegex. > > ^(aString matches: nonGrouped) or: > [(aString matches: grouped) and: > [aString size = 10 + 3]] > > Surely, you could cleverly compress the regex even further but that does > not matter for this example. After checking the syntax, you can just > iterate over the string and compute the check-digit on the fly. > > Kind regards, > Steffen > > Am .09.2020, 18:19 Uhr, schrieb Roelof Wobben via Pharo-users > <pharo-users(a)lists.pharo.org>: > >> See here for all the tests : >> https://github.com/exercism/pharo-smalltalk/blob/master/exercises/isbn-veri… >> >> Roelof >> >> >>

Sept. 7, 2020

Re: [Pharo-users] Can it do this way ?

by Steffen MÃ¤rcker

Hi, after reading the link and some additional sources, it turns out that a valid ISBN-10 has either no separators or four blocks separated by either dashes or spaces: Group-Publisher-Title-CheckDigit Assuming Regex11 (and that I made no mistake), the following should do the trick: IsbnVarifier>>isSyntacticIsbn: aString "no groups" noGrouped := '\d{9}[0-9X]' asRegex. "groups separated by either dashes or spaces" dashes := '\d{1,7}-\d{1,7}-\d{1,7}-[0-9X]' spaces := '\d{1,7} \d{1,7} \d{1,7} [0-9X]' grouped := (dashed , '|' , spaces) asRegex. ^(aString matches: nonGrouped) or: [(aString matches: grouped) and: [aString size = 10 + 3]] Surely, you could cleverly compress the regex even further but that does not matter for this example. After checking the syntax, you can just iterate over the string and compute the check-digit on the fly. Kind regards, Steffen Am .09.2020, 18:19 Uhr, schrieb Roelof Wobben via Pharo-users <pharo-users(a)lists.pharo.org>: > See here for all the tests : > https://github.com/exercism/pharo-smalltalk/blob/master/exercises/isbn-veri… > > Roelof > > >

Sept. 7, 2020

Re: [Pharo-users] Getting rid of .sources file for deployment

by Esteban Maringolo

Hi Stef, I don't know what's the demand for such a feature. In the Windows and Desktop era it might have been very important, but I don't see that kind of integration these days, when most system integrations happen at the HTTP level. For my particular case I don't need a DLL. Regards! Esteban A. Maringolo On Mon, Sep 7, 2020 at 1:55 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > I would like also to be able to deploy a pharo app as a dll juts time and money. > > S. > > On 7 Sep 2020, at 17:28, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > Hi Davide, > > Thanks for the thorough response, but I think you're over > dimensioning, and to some extent missing, my initial purpose and > intention. > > I don't want to protect from somebody attempting to reverse engineer > my application, that's impossible (more so given your references). > I simply want to disable the option to open the IDE, even with all > tool menus disabled. > > In Java if I deliver a .jar or .war anybody could reverse engineer it, > but launching it won't open the development environment. > > For comparison with other Smalltalks I've used: > * VisualWorks enables the distribution of a "headless" IMAGE (and > parcels) without sources, if you revert that image to be headful all > source code will be decompiled using meaningless variables. > * Dolphin has the concept of SessionManager that is the entry point to > the image startup, if you save your image with a Headless Session > manager, then no GUI loop will start, same thing if you deploy as a > COM component. > * VAST produces its own ICX file where you can choose what to include > in it, it's not simply saving the image but building a new one from > within the development image, it's one step further. > * VSE had the SLL (similar to DLLs), if you don't bind the IDE's SLLs > then there is no way to start the IDE (I never built a headless VSE > app though). > > So what I'd like is an always Pharo headless image or Pharo headless > vm, instead of being controlled by a parameter in the VM. > > Regards, > > Esteban A. Maringolo > > On Mon, Sep 7, 2020 at 12:04 PM Davide Grandi <davide.grandi(a)email.it> wrote: > > > Ok, I'll give you a result, meanwhile fixing some imprecisions. > > The "class" is CogVmSimulator but it's use is very far from my knowlegde, > I recalled having seen a picture of Pharo-in-Pharo (or Squeak-in-Squeak) > running under this simulator. > It lives near the Cog side (or the OpenVM side) of Squeak/Pharo > (If I'm not wrong Squeak ran into an emulator, before walking on his > legs-his VM). > > There are many of these simulator, for other Smalltalk : > - Hobbes and others for Xerox (thanks to files of Mario Molczko and/or > Bitsavers > - Dan Ingalls Apda Smalltalk + old Smalltalk -72 /-76 > and maybe others I don't yet know about > > The reason is quite simple : the object memory is written to disk > and the spec of executing Smalltalk are known either from the books > or by the source. > > The root is Xerox's SystemTracer, a class that wrote a running image > to disk, optionally changing object format (see the Green Book). > > So : > - if you can read the image > - you can run into a simulator > - or decode it without to much effort (5 emulators for Xerox V2 image, > so far). > (try to open an image with a text editor : intriguing !) > > I don't know how Cincom or Instantiations protect the released st code, > but for Pharo and Squeak this is not a point : they are all open. > > So, as if you wanna "protect" names and methods of a running image ... > ... you have to (IMHO) : > - encrypt executable and image (and modify the VM) > - or obfuscate your classes and methods renaming it to > C1, C2, ..., m1:p1:p2: and so on (keeping a map for debugging) > > Sorry to be imprecise about names and locations > apart from suggest to see 4 emulators 4 running in a squeak image > running ... in javascript in your browser (so total is 5) at : > https://smalltalkzoo.thechm.org/HOPL-Squeak.html?earlyst80 > (thanks to Vanessa Freudemberg & Dan Ingalls). > > Sorry again & best regards, > > Davide Grandi > > On 06/09/2020 23:51, Esteban Maringolo wrote: > > If somebody gets to open the image and loads it with an Smalltalk > Emulator to execute it I'll ask him/her to start working together, and > even teach me how to do it. > > I don't want to shield the image from being accessed, just want to > make it harder than simply removing the '--headless' parameter to the > VM executable. > Of course removing sources is a plus (I do for a VW deployed image), > but even for this particular piece of software that I'm asking for, I > don't need it. > > If I wanted to make the source public, I'll publish it in > Github/Gitlab, otherwise I'd rather keep the code private. > > Regards, > > Esteban A. Maringolo > > On Sun, Sep 6, 2020 at 6:29 PM Davide Grandi <davide.grandi(a)email.it> wrote: > > I mean that with SmalltalkEmulator, the Smalltalk interpreter > written in Smalltalk, one can execute an image looking at > classes, methods and maybe executing code at will. > > And the only practical form of protection I see in Squeak/Pharo > is to obfuscate code. > > Maybe I'm wrong. > > Davide Grandi > > On 06/09/2020 22:27, Esteban Maringolo wrote: > > On Sun, Sep 6, 2020 at 12:52 PM Davide Grandi <davide.grandi(a)email.it> wrote: > > Does "competition" has SmalltalkEmulator ? > A Smalltalk-written VM will defeat any simple obfuscation scheme. > > Sorry, but I don't understand what you mean. > > Best regards, > > -- > Ing. Davide Grandi > email : davide.grandi(a)email.it > mobile : +39 339 7468 778 > linkedin : http://linkedin.com/in/davidegrandi > > > -- > Ing. Davide Grandi > email : davide.grandi(a)email.it > mobile : +39 339 7468 778 > linkedin : http://linkedin.com/in/davidegrandi > > > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France >

Sept. 7, 2020

Re: [Pharo-users] Getting rid of .sources file for deployment

by StÃ©phane Ducasse

I would like also to be able to deploy a pharo app as a dll juts time and money. S. > On 7 Sep 2020, at 17:28, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > Hi Davide, > > Thanks for the thorough response, but I think you're over > dimensioning, and to some extent missing, my initial purpose and > intention. > > I don't want to protect from somebody attempting to reverse engineer > my application, that's impossible (more so given your references). > I simply want to disable the option to open the IDE, even with all > tool menus disabled. > > In Java if I deliver a .jar or .war anybody could reverse engineer it, > but launching it won't open the development environment. > > For comparison with other Smalltalks I've used: > * VisualWorks enables the distribution of a "headless" IMAGE (and > parcels) without sources, if you revert that image to be headful all > source code will be decompiled using meaningless variables. > * Dolphin has the concept of SessionManager that is the entry point to > the image startup, if you save your image with a Headless Session > manager, then no GUI loop will start, same thing if you deploy as a > COM component. > * VAST produces its own ICX file where you can choose what to include > in it, it's not simply saving the image but building a new one from > within the development image, it's one step further. > * VSE had the SLL (similar to DLLs), if you don't bind the IDE's SLLs > then there is no way to start the IDE (I never built a headless VSE > app though). > > So what I'd like is an always Pharo headless image or Pharo headless > vm, instead of being controlled by a parameter in the VM. > > Regards, > > Esteban A. Maringolo > > On Mon, Sep 7, 2020 at 12:04 PM Davide Grandi <davide.grandi(a)email.it> wrote: >> >> Ok, I'll give you a result, meanwhile fixing some imprecisions. >> >> The "class" is CogVmSimulator but it's use is very far from my knowlegde, >> I recalled having seen a picture of Pharo-in-Pharo (or Squeak-in-Squeak) >> running under this simulator. >> It lives near the Cog side (or the OpenVM side) of Squeak/Pharo >> (If I'm not wrong Squeak ran into an emulator, before walking on his >> legs-his VM). >> >> There are many of these simulator, for other Smalltalk : >> - Hobbes and others for Xerox (thanks to files of Mario Molczko and/or >> Bitsavers >> - Dan Ingalls Apda Smalltalk + old Smalltalk -72 /-76 >> and maybe others I don't yet know about >> >> The reason is quite simple : the object memory is written to disk >> and the spec of executing Smalltalk are known either from the books >> or by the source. >> >> The root is Xerox's SystemTracer, a class that wrote a running image >> to disk, optionally changing object format (see the Green Book). >> >> So : >> - if you can read the image >> - you can run into a simulator >> - or decode it without to much effort (5 emulators for Xerox V2 image, >> so far). >> (try to open an image with a text editor : intriguing !) >> >> I don't know how Cincom or Instantiations protect the released st code, >> but for Pharo and Squeak this is not a point : they are all open. >> >> So, as if you wanna "protect" names and methods of a running image ... >> ... you have to (IMHO) : >> - encrypt executable and image (and modify the VM) >> - or obfuscate your classes and methods renaming it to >> C1, C2, ..., m1:p1:p2: and so on (keeping a map for debugging) >> >> Sorry to be imprecise about names and locations >> apart from suggest to see 4 emulators 4 running in a squeak image >> running ... in javascript in your browser (so total is 5) at : >> https://smalltalkzoo.thechm.org/HOPL-Squeak.html?earlyst80 >> (thanks to Vanessa Freudemberg & Dan Ingalls). >> >> Sorry again & best regards, >> >> Davide Grandi >> >> On 06/09/2020 23:51, Esteban Maringolo wrote: >>> If somebody gets to open the image and loads it with an Smalltalk >>> Emulator to execute it I'll ask him/her to start working together, and >>> even teach me how to do it. >>> >>> I don't want to shield the image from being accessed, just want to >>> make it harder than simply removing the '--headless' parameter to the >>> VM executable. >>> Of course removing sources is a plus (I do for a VW deployed image), >>> but even for this particular piece of software that I'm asking for, I >>> don't need it. >>> >>> If I wanted to make the source public, I'll publish it in >>> Github/Gitlab, otherwise I'd rather keep the code private. >>> >>> Regards, >>> >>> Esteban A. Maringolo >>> >>> On Sun, Sep 6, 2020 at 6:29 PM Davide Grandi <davide.grandi(a)email.it> wrote: >>>> I mean that with SmalltalkEmulator, the Smalltalk interpreter >>>> written in Smalltalk, one can execute an image looking at >>>> classes, methods and maybe executing code at will. >>>> >>>> And the only practical form of protection I see in Squeak/Pharo >>>> is to obfuscate code. >>>> >>>> Maybe I'm wrong. >>>> >>>> Davide Grandi >>>> >>>> On 06/09/2020 22:27, Esteban Maringolo wrote: >>>>> On Sun, Sep 6, 2020 at 12:52 PM Davide Grandi <davide.grandi(a)email.it> wrote: >>>>>> Does "competition" has SmalltalkEmulator ? >>>>>> A Smalltalk-written VM will defeat any simple obfuscation scheme. >>>>> Sorry, but I don't understand what you mean. >>>>> >>>>> Best regards, >>>> -- >>>> Ing. Davide Grandi >>>> email : davide.grandi(a)email.it >>>> mobile : +39 339 7468 778 >>>> linkedin : http://linkedin.com/in/davidegrandi >> >> -- >> Ing. Davide Grandi >> email : davide.grandi(a)email.it >> mobile : +39 339 7468 778 >> linkedin : http://linkedin.com/in/davidegrandi >> >> > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Sept. 7, 2020

Re: [Pharo-users] Can it do this way ?

by Roelof Wobben

See here for all the tests : https://github.com/exercism/pharo-smalltalk/blob/master/exercises/isbn-veri… Roelof

Sept. 7, 2020

Re: [Pharo-users] Getting rid of .sources file for deployment

by Esteban Maringolo

Hi Davide, Thanks for the thorough response, but I think you're over dimensioning, and to some extent missing, my initial purpose and intention. I don't want to protect from somebody attempting to reverse engineer my application, that's impossible (more so given your references). I simply want to disable the option to open the IDE, even with all tool menus disabled. In Java if I deliver a .jar or .war anybody could reverse engineer it, but launching it won't open the development environment. For comparison with other Smalltalks I've used: * VisualWorks enables the distribution of a "headless" IMAGE (and parcels) without sources, if you revert that image to be headful all source code will be decompiled using meaningless variables. * Dolphin has the concept of SessionManager that is the entry point to the image startup, if you save your image with a Headless Session manager, then no GUI loop will start, same thing if you deploy as a COM component. * VAST produces its own ICX file where you can choose what to include in it, it's not simply saving the image but building a new one from within the development image, it's one step further. * VSE had the SLL (similar to DLLs), if you don't bind the IDE's SLLs then there is no way to start the IDE (I never built a headless VSE app though). So what I'd like is an always Pharo headless image or Pharo headless vm, instead of being controlled by a parameter in the VM. Regards, Esteban A. Maringolo On Mon, Sep 7, 2020 at 12:04 PM Davide Grandi <davide.grandi(a)email.it> wrote: > > Ok, I'll give you a result, meanwhile fixing some imprecisions. > > The "class" is CogVmSimulator but it's use is very far from my knowlegde, > I recalled having seen a picture of Pharo-in-Pharo (or Squeak-in-Squeak) > running under this simulator. > It lives near the Cog side (or the OpenVM side) of Squeak/Pharo > (If I'm not wrong Squeak ran into an emulator, before walking on his > legs-his VM). > > There are many of these simulator, for other Smalltalk : > - Hobbes and others for Xerox (thanks to files of Mario Molczko and/or > Bitsavers > - Dan Ingalls Apda Smalltalk + old Smalltalk -72 /-76 > and maybe others I don't yet know about > > The reason is quite simple : the object memory is written to disk > and the spec of executing Smalltalk are known either from the books > or by the source. > > The root is Xerox's SystemTracer, a class that wrote a running image > to disk, optionally changing object format (see the Green Book). > > So : > - if you can read the image > - you can run into a simulator > - or decode it without to much effort (5 emulators for Xerox V2 image, > so far). > (try to open an image with a text editor : intriguing !) > > I don't know how Cincom or Instantiations protect the released st code, > but for Pharo and Squeak this is not a point : they are all open. > > So, as if you wanna "protect" names and methods of a running image ... > ... you have to (IMHO) : > - encrypt executable and image (and modify the VM) > - or obfuscate your classes and methods renaming it to > C1, C2, ..., m1:p1:p2: and so on (keeping a map for debugging) > > Sorry to be imprecise about names and locations > apart from suggest to see 4 emulators 4 running in a squeak image > running ... in javascript in your browser (so total is 5) at : > https://smalltalkzoo.thechm.org/HOPL-Squeak.html?earlyst80 > (thanks to Vanessa Freudemberg & Dan Ingalls). > > Sorry again & best regards, > > Davide Grandi > > On 06/09/2020 23:51, Esteban Maringolo wrote: > > If somebody gets to open the image and loads it with an Smalltalk > > Emulator to execute it I'll ask him/her to start working together, and > > even teach me how to do it. > > > > I don't want to shield the image from being accessed, just want to > > make it harder than simply removing the '--headless' parameter to the > > VM executable. > > Of course removing sources is a plus (I do for a VW deployed image), > > but even for this particular piece of software that I'm asking for, I > > don't need it. > > > > If I wanted to make the source public, I'll publish it in > > Github/Gitlab, otherwise I'd rather keep the code private. > > > > Regards, > > > > Esteban A. Maringolo > > > > On Sun, Sep 6, 2020 at 6:29 PM Davide Grandi <davide.grandi(a)email.it> wrote: > >> I mean that with SmalltalkEmulator, the Smalltalk interpreter > >> written in Smalltalk, one can execute an image looking at > >> classes, methods and maybe executing code at will. > >> > >> And the only practical form of protection I see in Squeak/Pharo > >> is to obfuscate code. > >> > >> Maybe I'm wrong. > >> > >> Davide Grandi > >> > >> On 06/09/2020 22:27, Esteban Maringolo wrote: > >>> On Sun, Sep 6, 2020 at 12:52 PM Davide Grandi <davide.grandi(a)email.it> wrote: > >>>> Does "competition" has SmalltalkEmulator ? > >>>> A Smalltalk-written VM will defeat any simple obfuscation scheme. > >>> Sorry, but I don't understand what you mean. > >>> > >>> Best regards, > >> -- > >> Ing. Davide Grandi > >> email : davide.grandi(a)email.it > >> mobile : +39 339 7468 778 > >> linkedin : http://linkedin.com/in/davidegrandi > > -- > Ing. Davide Grandi > email : davide.grandi(a)email.it > mobile : +39 339 7468 778 > linkedin : http://linkedin.com/in/davidegrandi > >

Sept. 7, 2020

Re: [Pharo-users] Getting rid of .sources file for deployment

by Davide Grandi

Ok, I'll give you a result, meanwhile fixing some imprecisions. The "class" is CogVmSimulator but it's use is very far from my knowlegde, I recalled having seen a picture of Pharo-in-Pharo (or Squeak-in-Squeak) running under this simulator. It lives near the Cog side (or the OpenVM side) of Squeak/Pharo (If I'm not wrong Squeak ran into an emulator, before walking on his legs-his VM). There are many of these simulator, for other Smalltalk : - Hobbes and others for Xerox (thanks to files of Mario Molczko and/or Â Bitsavers - Dan Ingalls Apda Smalltalk + old Smalltalk -72 /-76 and maybe others I don't yet know about The reason is quite simple : the object memory is written to disk and the spec of executing Smalltalk are known either from the books or by the source. The root is Xerox's SystemTracer, a class that wrote a running image to disk, optionally changing object format (see the Green Book). So : - if you can read the image - you can run into a simulator - or decode it without to much effort (5 emulators for Xerox V2 image, so far). (try to open an image with a text editor : intriguing !) I don't know how Cincom or Instantiations protect the released st code, but for Pharo and Squeak this is not a point : they are all open. So, as if you wanna "protect" names and methods of a running image ... ... you have to (IMHO) : - encrypt executable and image (and modify the VM) - or obfuscate your classes and methods renaming it to Â C1, C2, ..., m1:p1:p2: and so on (keeping a map for debugging) Sorry to be imprecise about names and locations apart from suggest to see 4 emulators 4 running in a squeak image running ... in javascript in your browser (so total is 5) at : https://smalltalkzoo.thechm.org/HOPL-Squeak.html?earlyst80 (thanks to Vanessa Freudemberg & Dan Ingalls). Sorry again & best regards, Â Â Â Davide Grandi On 06/09/2020 23:51, Esteban Maringolo wrote: > If somebody gets to open the image and loads it with an Smalltalk > Emulator to execute it I'll ask him/her to start working together, and > even teach me how to do it. > > I don't want to shield the image from being accessed, just want to > make it harder than simply removing the '--headless' parameter to the > VM executable. > Of course removing sources is a plus (I do for a VW deployed image), > but even for this particular piece of software that I'm asking for, I > don't need it. > > If I wanted to make the source public, I'll publish it in > Github/Gitlab, otherwise I'd rather keep the code private. > > Regards, > > Esteban A. Maringolo > > On Sun, Sep 6, 2020 at 6:29 PM Davide Grandi <davide.grandi(a)email.it> wrote: >> I mean that with SmalltalkEmulator, the Smalltalk interpreter >> written in Smalltalk, one can execute an image looking at >> classes, methods and maybe executing code at will. >> >> And the only practical form of protection I see in Squeak/Pharo >> is to obfuscate code. >> >> Maybe I'm wrong. >> >> Davide Grandi >> >> On 06/09/2020 22:27, Esteban Maringolo wrote: >>> On Sun, Sep 6, 2020 at 12:52 PM Davide Grandi <davide.grandi(a)email.it> wrote: >>>> Does "competition" has SmalltalkEmulator ? >>>> A Smalltalk-written VM will defeat any simple obfuscation scheme. >>> Sorry, but I don't understand what you mean. >>> >>> Best regards, >> -- >> Ing. Davide Grandi >> email : davide.grandi(a)email.it >> mobile : +39 339 7468 778 >> linkedin : http://linkedin.com/in/davidegrandi -- Ing. Davide Grandi email : davide.grandi(a)email.it mobile : +39 339 7468 778 linkedin : http://linkedin.com/in/davidegrandi

Sept. 7, 2020

Re: [Pharo-users] Can it do this way ?

by Steffen MÃ¤rcker

No problem. I am not knowledgeable about isbn numbers. At which places may a dash occur? Kind regards, Steffen 07.09.2020 16:18:22 Roelof Wobben via Pharo-users <pharo-users(a)lists.pharo.org>: > Op 6-9-2020 om 10:07 schreef Steffen MÃ¤rcker: >> Maybe this is a naive question, but can you just split the task into the >> following two? >> >> 1. Check whether whether the string is syntactically an ISBN number. >> This can be done, e.g., using a regex. >> >> 2. Check the the check character. >> Calculate the check character from the (now to be known) syntactically >> valid string. >> >> ISBNValidator>>isValidISBN: aString >> ^(self isSyntacticallyValid: aString) and: [self isCheckCharacterValid: >> aString] >> >> Kind regards, >> Steffen nder if the code will not be too big. I learned that it is good >> > Sorry to respond not earlier but your respons seems to be in the spam folder of my provider. > > I could do that but if very bad in regex so I do not know a regex which van validate 123456789 or 123-456-78-9 > > Roelof >

Sept. 7, 2020