smallwiki May 2015

smallwiki@list.inf.unibe.ch

10 participants
14 discussions

by Sean P. DeNigris

What do you think of the following error handling? If an error is encountered converting a string to the underlying domain object, it silently passes the raw string back to the model. This led to a very difficult to trace bug in my code. Is there a valid reason to hide the error that makes it worth the confusion? MAElementMorph>>#string: aString | value | value := [ self magritteDescription fromString: aString greaseString ] on: Error do: [ :e | aString ]. self value: value; changed: #string ----- Cheers, Sean -- View this message in context: http://forum.world.st/MAElementMorphs-Hide-Errors-tp4820869.html Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.

8 years, 11 months

Re: [Pharo-dev] [Moose-dev] [SURVEY] Pillar input/output files.

by Cyril Ferlicot

Hi, I think we'll be able to avoid what i've expose on the first message. I changed the way Pillar parsed the files so it's not easier to create a global numerator or inter file links. When i'll have something that work i'll do a new configuration a post a message on the ML. On 18 May 2015 at 22:53, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Cyril, > > It does not look that different. Something I may recommend, is that Pillar > should be effective at writing other things than a book. So, the chapter > decomposition should not be forced. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On May 4, 2015, at 7:38 AM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > I'm currently working on the way we manage the input files and the output > files. > The way we manage the files now makes hard some improvement of Pillar. > That's why with Damien we though about makes some changes. The changes > are big so I wanted to talk about that with you. > We propose to have always 1 file with all the work inside. That can > use the inputFile tag. For example: > > "${inputFile:Chapter1.pillar}$ > > ${inputFile:Chapter2.pillar}$ > > ${inputFile:Chapter3.pillar}$ > > ${inputFile:Chapter4.pillar}$" > > And the option "separateOutputFiles" will now create 1 file each time > we have a new Chapter. (!Level 1 header). > That will make simpler the way to number everything and to create > anchor because those 2 doesn't work well with the "separateOutputFile" > option. > > What do you thing? That would be good with you? > > -- > Cheers > Cyril Ferlicot > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- Cheers Cyril Ferlicot

8 years, 11 months

Re: [Pharo-dev] [Pharo-users] [SURVEY] Pillar input/output files.

by Guillermo Polito

If I understand correctly... then, why the pillar.conf is not just a pillar file? (And the conf is the header if the file?) :) El lun., 4 de may. de 2015 a la(s) 2:50 p. m., Damien Cassou < damien.cassou(a)inria.fr> escribió: > > Cyril Ferlicot <cyril.ferlicot(a)gmail.com> writes: > > > Hi, > > I'm currently working on the way we manage the input files and the > output files. > > The way we manage the files now makes hard some improvement of Pillar. > > That's why with Damien we though about makes some changes. The changes > > are big so I wanted to talk about that with you. > > We propose to have always 1 file with all the work inside. That can > > use the inputFile tag. For example: > > > > "${inputFile:Chapter1.pillar}$ > > > > ${inputFile:Chapter2.pillar}$ > > > > ${inputFile:Chapter3.pillar}$ > > > > ${inputFile:Chapter4.pillar}$" > > > > And the option "separateOutputFiles" will now create 1 file each time > > we have a new Chapter. (!Level 1 header). > > That will make simpler the way to number everything and to create > > anchor because those 2 doesn't work well with the "separateOutputFile" > > option. > > > > What do you thing? That would be good with you? > > this change proposes to remove the option inputFiles from Pillar. Pillar > will now take only 1 Pillar input file that must include the rest. This > will simplify pillar.conf, this will simplify compile.sh, this will make > it easier for the author to understand the process, and this will > simplify Pillar's implementation. With this in place, we think we can > fix the problems with anchors and inter-chapter links. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > >

8 years, 11 months

[SURVEY] Pillar input/output files.

by Cyril Ferlicot

Hi, I'm currently working on the way we manage the input files and the output files. The way we manage the files now makes hard some improvement of Pillar. That's why with Damien we though about makes some changes. The changes are big so I wanted to talk about that with you. We propose to have always 1 file with all the work inside. That can use the inputFile tag. For example: "${inputFile:Chapter1.pillar}$ ${inputFile:Chapter2.pillar}$ ${inputFile:Chapter3.pillar}$ ${inputFile:Chapter4.pillar}$" And the option "separateOutputFiles" will now create 1 file each time we have a new Chapter. (!Level 1 header). That will make simpler the way to number everything and to create anchor because those 2 doesn't work well with the "separateOutputFile" option. What do you thing? That would be good with you? -- Cheers Cyril Ferlicot

8 years, 11 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

smallwiki May 2015