July 2018 - Pharo-users - lists.pharo.org

ZnCharacterWriteStream â is it a WriteStream?

by Andrew P. Black

Iâm making a stream to write on a file using outputFile := FileLocator home / 'Desktop' / classBeingTranslated name , '.grace'. outputFile writeStreamDo: [ :s | ... ] Is that OK? When I do the above, in the writeStreamDo: block, s is bound to an instance of ZnCharacterWriteStream. But that class does nt understand many methods from WriteStream. For example, #contents is not understood, and nor is #ensureASpace. To put things another way: I wrote tests using a stream created with String streamContents: [ :s | ... ], and everything worked fine. Then, for production use, I switch to a stream created using outputFile writeStreamDo: [ :s | ... ] and everything breaks. I know that ZnCharacterWriteStream is fairly new. Am I doing something wrong, or is ZnCharacterWriteStream still under development? Andrew

July 31, 2018

Re: [Pharo-users] [ANN] Pharo Git Thermite Release

by Andrew Black

Hi Ronie, These visualizations look great! But I donât know what they /mean/. When one hovers the mouse over the visualizations, does help text appear explaining what one is looking at? For example, I guess that the red and green segments in âLines of Codeâ refer to lines deleted and added. But what are the green and yellow for âClassesâ. And whatâs a âFunctionâ in Pharo? The more complicated diagram for âRoassal2â I canât even begin to guess at! Donât make the mistake of thinking that because you know what the diagram means, after working on it for months, that other programmers will also know. Andrew

July 31, 2018

Re: [Pharo-dev] Charting in Roassal2

by Alexandre Bergel

Hi! Roassal supports Whisker plots, but not exactly candlestick. You can try this: -=-=-=-=-=-=-=-=-=-=-=-= | b createList r | r := Random new. createList := [ :size :d1 :d2 | (1 to: size) collect: [ :i | d1 + (r next * (d2-d1))] ]. b := RTGrapher new. (1 to: 10) do: [ :i | | ds | ds := RTBoxPlotDataSet new. ds points: (createList value: 20 value: 0 value: 20). b add: ds.]. b -=-=-=-=-=-=-=-=-=-=-=-= Which produces: Another example: =-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-= | b ds | b := RTGrapher new. b extent: 400 @ 200. RTShape withAllSubclasses do: [ :cls | ds := RTBoxPlotDataSet new. ds points: (cls rtmethods collect: #numberOfLinesOfCode). b add: ds ]. ^ b =-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-= Which shows the distribution of methods size in Roassal Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jul 27, 2018, at 8:47 PM, Shaping <shaping(a)uurda.org> wrote: > > Hi Folks. > > Can anyone tell me whether we have candlestick-charting ability in Roassal2? > > > Shaping

July 31, 2018

Re: [Pharo-users] Pharo 7 file streams guideline

by Damien Pollet

On Tue, 31 Jul 2018 at 18:28, Damien Pollet <damien.pollet+pharo(a)gmail.com> wrote: > Hi Svenâ¦ a couple questions: > For context, I'm considering options in Clap, for providing accessors to Stdio that: - are convenient in most cases - discourage users from explicitly referencing the Stdio global (so that one can inject other streams instead if needed) For instance, it seems to make sense to provide stdout already wrapped with ZnNewLineWriterStream, but that precludes users from buffering. - is there a preferred order of composition between the encoding and > buffering streams ? If yes, it the same for read and write stream, or > reversed ? > E.g. if Stdio binaryStdin was implemented, Stdio stdin should be decoded, > but buffering it as well would be a problem for interactive applications. > > - what's your opinion on convenience composition messages, e.g. > aBinaryStream buffered decoded: 'utf-8' ? > > > > On Tue, 24 Jul 2018 at 10:13, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> >> > On 23 Jul 2018, at 12:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> > >> > Stdio stdout and friends just return a binary stream, hence they need >> wrapping for encoding. >> > >> > Maybe >> > >> > Stdio stdoutAsText >> > >> > might be an idea, but this is so uncommon that I am not sure this is a >> good idea. >> >> Given all remarks and comments (thanks BTW), I now think that >> >> - textual stdio streams are the more common case >> - binary stdio streams are the primitive ones that are seldom used >> - another encoding than UTF-8 seems uncommon >> - these are streams that exist and need no real opening/closing >> >> So, >> >> Stdio stdout >> >> should return return a character write stream with UTF-8 encoding while >> >> Stdio binaryStdout >> >> should be the lower level binary one. >> This would be more in line with the other streams. >> A non-UTF-8 encoding can be used as per Pavel's example. >> >

July 31, 2018

Re: [Pharo-users] Pharo 7 file streams guideline

by Damien Pollet

Hi Svenâ¦ a couple questions: - is there a preferred order of composition between the encoding and buffering streams ? If yes, it the same for read and write stream, or reversed ? E.g. if Stdio binaryStdin was implemented, Stdio stdin should be decoded, but buffering it as well would be a problem for interactive applications. - what's your opinion on convenience composition messages, e.g. aBinaryStream buffered decoded: 'utf-8' ? On Tue, 24 Jul 2018 at 10:13, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 23 Jul 2018, at 12:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > Stdio stdout and friends just return a binary stream, hence they need > wrapping for encoding. > > > > Maybe > > > > Stdio stdoutAsText > > > > might be an idea, but this is so uncommon that I am not sure this is a > good idea. > > Given all remarks and comments (thanks BTW), I now think that > > - textual stdio streams are the more common case > - binary stdio streams are the primitive ones that are seldom used > - another encoding than UTF-8 seems uncommon > - these are streams that exist and need no real opening/closing > > So, > > Stdio stdout > > should return return a character write stream with UTF-8 encoding while > > Stdio binaryStdout > > should be the lower level binary one. > This would be more in line with the other streams. > A non-UTF-8 encoding can be used as per Pavel's example. >

July 31, 2018

Re: [Pharo-users] a basic hash question

by James Foster

To what extent is it required by ANSI that objects be of the same class? Does Pharo treat a String and a Symbol as equivalent if they have the same characters? James > On Jul 30, 2018, at 10:59 PM, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > I do not think that (1 to: 4) and #(1 2 3 4) should be equal. > Let me put it a little more strongly: it's a bug. > Taking > a := 1 to: 4. > b := Array withAll: a. > c := OrderedCollection withAll: b. > in the two other Smalltalk systems I just tried, > no two of these are equal. This is what the ANSI > Smalltalk standard requires. Ceteris paribus, > two sequences are equivalent if and only if > 1. they are instance of the same class > 2. they have the same size > 3. corresponding elements are equivalent. > It is fairly common for Smalltalk systems to distinguish > between "these sequences are equivalent" and "these > sequences have the same elements in the same order", > with no consensus on the name of the second method. > One calls it #sameContentsAs:, Squeak #hasEqualElements:. > > > On 31 July 2018 at 00:07, werner kassens <wkassens(a)libello.com <mailto:wkassens@libello.com>> wrote: > Hi, > i guess i can subsume almost everything i know about hashes in one sentence: > it is my understanding that two objects that are equal (obj1=obj2. > -->true) have to have the same hash value (which is used for some > collection types), whereas objects where obj1=obj2 returns false should > have different hash values although it may happen that they have the > same one. > > now here things don't turn out exactly like that: > (1 to:4) = #(1 2 3 4). "true" > (1 to:4)hash = #(1 2 3 4)hash. "false" > well ok, actually these results make - pfffh, in a certain way - sense > to me, but i wonder what arguments the people in the know would use to > defend that result, if i would have another opinion? > werner > > >

July 31, 2018

Re: [Pharo-users] [Moose-dev] Moose Java AST?

by Tudor Girba

Hi, There is one in the SmaCC that ships with Moose: JavaParser. Cheers, Doru > On Jul 31, 2018, at 10:44 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > is there a Java AST parser in Pharo? > > I imagine that jdt2famix must have something inside, but as far as I understand, it just extracts some information from the source code and throws the AST away. > > Thanks, > Peter > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Not knowing how to do something is not an argument for how it cannot be done."

July 31, 2018

Pillar Book Tester

by Quentin DUCASSE (CI_2020)

Hello everyone! I am currently in an internship within the RMoD team and would like to present my work. My internship subject was the following: âHow to test documents (books, slides) written in Pillar?â. Let me first introduce Pillar then what I managed to implement and what is left to do. -What is Pillar? Pillar is a markup syntax and associated tools to write and generate documentation, books, slide-based presentations or websites. Pillar syntax is similar to Markdownâs one but its emphasis is stressed on publishing to different formats/languages (Markdown, html, LateX, pdf). -What does it mean to âtest a bookâ? -- Display code within the book Pillar syntax allows you to write codeblocks, showing a part of code. The inside of a codeblock allows one to display any part of code you might want to. For example: [[[ YourClass >> yourMethod ^ âblaâ ]]] This codeblock presents a method definition, the other two possible codeblocks are the following: Class definition [[[ Object subclass: #YourClass instanceVariableNames: '' classVariableNames: '' package: YourPackage' ]]] Example [[[ 1+1 >>> 2 ]]] -- How to test it? The use of â>>>â and parameters in the codeblock will help us to test the code within it. The BookTester will turn examples into tests. Testing examples: [[[testcase=true 3+4 becomes self assert: (3+4) equals: 7 >>>7 ]]] Testing methodDefinitions and classDefinitions: Testing method or class definitions resumes is the same as testing if the compilation of the method does not raise any error. It can help make sure your book is up to date with the latest Pharo version. Those tests are done the same way as testing an example: stating methodDefinition=true or classDefinition=true as code block parameters will make them elible for tests. Now, we are adding more features to code block or Pillar to help book writers. -Additional Features In Pillar, several annotations can be used for different purposes like including columns/tables/citations/figures/linksâ¦ -- Loading code: loader ${loader:account=QDucasse|project=TestBook|tag=Chapter1}$ allows you to load the github project as it was in the commit tagged Chapter1. This will help you test every chapter of your code with its current progression and also allow you to test the objects you are defining in your book. - Executing Tests: run ${run:testClass=YourClassTest}$ runs the test defined in the class testClass. And of course this testClass can be Other annotations have been added to help you write your book: - Display a class definition: showClass: ${showClass:className=YourClass}$ displays a codeblock with the class definition within it This helps you quickly include a class definition you want to display in your book. Combined with the loader it means that the code can be the source of your book. - Display a method definition: showMethod: ${showMethod:className=YourClass|methodName=yourMethod}$ will display a codeblock with the method definition within it This helps you quickly include a method definition you want to display in your book. - Screenshot: ${showMethod:packageName=yourPackage|className=YourClass|methodName=yourMethod|caption|width|label}$ saves a screenshot of a Calypso browser open at the selected package, class and method and includes it in both your book (using the designated Pillar figure reference) and the figures subfolder in the pillar book folder (saved as PNG). -Future objectives One of the future improvements would be to make everyone able to write examples and test them in the comments of method definitions. It is already partially possible â3+4 >>> 7â will be highlighted differently and if printed will display â7->7â. However, an automation or UI improvement would be nice. I hope this gave you the will to write something you had in mind. Are there any books you want to try the tools on? Feel free to ask ! Quentin Ducasse

July 31, 2018

Re: [Pharo-users] Moose Java AST?

by PBKResearch

Peter How about PPJavaParser or SmaCC-Java? Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Peter UhnÃ¡k Sent: 31 July 2018 09:44 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>; Moose-related development <moose-dev(a)list.inf.unibe.ch> Subject: [Pharo-users] Moose Java AST? Hi, is there a Java AST parser in Pharo? I imagine that jdt2famix must have something inside, but as far as I understand, it just extracts some information from the source code and throws the AST away. Thanks, Peter

July 31, 2018

Moose Java AST?

by Peter UhnÃ¡k

Hi, is there a Java AST parser in Pharo? I imagine that jdt2famix must have something inside, but as far as I understand, it just extracts some information from the source code and throws the AST away. Thanks, Peter

July 31, 2018