Thanks for all these comments!
On 05 Feb 2014, at 00:27, GitHub wrote:
> 30742
> 12794 Class comments missing in UpdateStreamer package
> https://pharo.fogbugz.com/f/cases/12794
>
> 12802 Class comments missing for Kernel package
> https://pharo.fogbugz.com/f/cases/12802
>
> 12804
bugz.com/f/cases/12812 for Spec)
step by step it goes ...
Bye
T.
Gesendet: Mittwoch, 05. Februar 2014 um 08:36 Uhr
Von: Pharo4Stef
An: "Pharo Development List"
Betreff: [Pharo-dev] comments :)
Thanks for all these comments!
On 05 Feb 2014, at 00:27, GitHub wrote: 30742
step by step it goes ...
Bye
T.
Gesendet: Mittwoch, 05. Februar 2014 um 08:36 Uhr
Von: Pharo4Stef
An: "Pharo Development List"
Betreff: [Pharo-dev] comments :)
Thanks for all these comments!
On 05 Feb 2014, at 00:27, GitHub wrote: 30742
12794 Class comments missing in Updat
onnerstag, 06. Februar 2014 um 10:43 Uhr
> Von: b...@openinworld.com
> An: "Pharo Development List"
> Betreff: Re: [Pharo-dev] comments :)
>
> Good work. Minor thing though - could they maybe grouped under one Case.
> I'd hate for someone to look at the massive amount w
ergin back into external managed parts.
> There was no reaction onto my call for action from others.
>
> So instead of grumbling afterwards better use your keyboard to comment on
> classes ;)
>
> Thx
> T.
>
> > Gesendet: Donnerstag, 06. Februar 2014 um 10:43 Uhr
> >
Hi Sven, list,
I'm using Pillar, and thus STON for its configuration file. And since I
want users to change configuration files as they want, I wanted to add some
comments explaining the meaning of the file fields.
This raises the question: How can I write comments in a ston file? I was
checking
I am not so sure we should add that.
The JSON spec explicitly does not allow comments because of fear of abuse (that
the comments would be used to add semantic meaning outside the spec).
I have to think about that.
In any case, I think comments with open/close are generally more useful.
> On
Sven Van Caekenberghe writes:
> I am not so sure we should add that.
>
> The JSON spec explicitly does not allow comments because of fear of abuse
> (that the comments would be used to add semantic meaning outside the spec).
really? That's surprising. Comments in configuration files are very
Le 8 juin 2015 à 17:03, Damien Cassou a écrit :
>
> Sven Van Caekenberghe writes:
>
>> I am not so sure we should add that.
>>
>> The JSON spec explicitly does not allow comments because of fear of abuse
>> (that the comments would be used to add semantic meaning outside the spec).
>
>
>
> On 08 Jun 2015, at 17:03, Damien Cassou wrote:
>
>
> Sven Van Caekenberghe writes:
>
>> I am not so sure we should add that.
>>
>> The JSON spec explicitly does not allow comments because of fear of abuse
>> (that the comments would be used to add semantic meaning outside the spec).
>
>
If not we could maybe write a yaml parser :)
http://yaml.org/
It has no brackets, it is also hierarchical and it supports comments.
El lun., 8 de jun. de 2015 a la(s) 5:16 p. m., Sven Van Caekenberghe <
s...@stfx.eu> escribió:
>
> > On 08 Jun 2015, at 17:03, Damien Cassou wrote:
> >
> >
> > Sv
Damien Cassou-2 wrote
> Sven Van Caekenberghe <
> sven@
> > writes:
>
>> I am not so sure we should add that.
>>
>> The JSON spec explicitly does not allow comments because of fear of abuse
>> (that the comments would be used to add semantic meaning outside the
>> spec).
>
>
> really? That's
I would do it like this: use a wrapping stream to skip comments.
===
Name: STON-Core-SvenVanCaekenberghe.59
Author: SvenVanCaekenberghe
Time: 8 June 2015, 11:34:32.886167 pm
UUID: 7ab942b5-9d1a-44c3-9d58-da29feb72380
Ancestors: STON-Core-SvenVanCaekenberghe.58
Add experimental STONCStyleCommentsS
Sven Van Caekenberghe writes:
> What do you think ?
this looks like a very good solution.
Thank you very much Sven
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
You are up very early ;-)
In #bleedingEdge (to be integrated in Pharo 5 later on):
===
Name: STON-Core-SvenVanCaekenberghe.60
Author: SvenVanCaekenberghe
Time: 9 June 2015, 11:04:57.955405 am
UUID: 7b95fcbe-1a44-4c94-a196-042e4cdb3e97
Ancestors: STON-Core-SvenVanCaekenberghe.59
Add 2 convenience
Cool!
Actually I just wanted comments as a way of self documentation. So ignoring
comments is more than enough for what I wanted :)
Thanks!
El mar., 9 de jun. de 2015 a la(s) 11:16 a. m., Sven Van Caekenberghe <
s...@stfx.eu> escribió:
> You are up very early ;-)
>
> In #bleedingEdge (to be int
so ugly!
Le 8/6/15 17:27, Guillermo Polito a écrit :
If not we could maybe write a yaml parser :)
http://yaml.org/
It has no brackets, it is also hierarchical and it supports comments.
El lun., 8 de jun. de 2015 a la(s) 5:16 p. m., Sven Van Caekenberghe
mailto:s...@stfx.eu>> escribió:
I will update the STON chapter :)
Le 8/6/15 23:39, Sven Van Caekenberghe a écrit :
I would do it like this: use a wrapping stream to skip comments.
===
Name: STON-Core-SvenVanCaekenberghe.59
Author: SvenVanCaekenberghe
Time: 8 June 2015, 11:34:32.886167 pm
UUID: 7ab942b5-9d1a-44c3-9d58-da29feb
Le 9/6/15 20:06, stepharo a écrit :
I will update the STON chapter :)
Done :)
Le 8/6/15 23:39, Sven Van Caekenberghe a écrit :
I would do it like this: use a wrapping stream to skip comments.
===
Name: STON-Core-SvenVanCaekenberghe.59
Author: SvenVanCaekenberghe
Time: 8 June 2015, 11:34
Where exactly can I find what you changed ?
I don't see any commit of you on github ...
> On 09 Jun 2015, at 20:10, stepharo wrote:
>
>
>
> Le 9/6/15 20:06, stepharo a écrit :
>> I will update the STON chapter :)
>
> Done :)
>
>>
>>
>> Le 8/6/15 23:39, Sven Van Caekenberghe a écrit :
>>> I
This is in the entreprise book. I added a subsection on comments.
May be I committed but forgot to push.
Now I did it.
Stef
Le 9/6/15 21:50, Sven Van Caekenberghe a écrit :
Where exactly can I find what you changed ?
I don't see any commit of you on github ...
On 09 Jun 2015, at 20:10, steph
> On 10 Jun 2015, at 15:13, stepharo wrote:
>
> This is in the entreprise book. I added a subsection on comments.
> May be I committed but forgot to push.
> Now I did it.
And now I see it.
I made a small change.
> Stef
>
>
> Le 9/6/15 21:50, Sven Van Caekenberghe a écrit :
>> Where exactly c
Le 10/6/15 20:39, Sven Van Caekenberghe a écrit :
On 10 Jun 2015, at 15:13, stepharo wrote:
This is in the entreprise book. I added a subsection on comments.
May be I committed but forgot to push.
Now I did it.
And now I see it.
I made a small change.
super!
Stef
Le 9/6/15 21:50, Sven
Hi Sven!
I'm finally using the new STON with comments and I found one little
problem: my ston file has urls :/
{
// comment ok, skipped
/* comment ok, skipped */
"aURL": "http://ouch.it.will.be.skipped/and/break?my=ston";
}
That is, doing:
STON fromStreamWithComments: '{
// comment ok, skippe
Guille,
I understand the problem.
The reason is that STONCStyleCommentsSkipStream was/is a quick hack and does
not know/understand anything about strings.
It seems that the C preprocessor ignores comments in C strings, so we could
consider adding that.
Basically STONCStyleCommentsSkipStream>>
Hi sven
Le 16/7/15 21:28, Sven Van Caekenberghe a écrit :
Guille,
I understand the problem.
The reason is that STONCStyleCommentsSkipStream was/is a quick hack and does
not know/understand anything about strings.
It seems that the C preprocessor ignores comments in C strings, so we could
c
> On 17 Jul 2015, at 09:00, stepharo wrote:
>
> Hi sven
>
>
> Le 16/7/15 21:28, Sven Van Caekenberghe a écrit :
>> Guille,
>>
>> I understand the problem.
>>
>> The reason is that STONCStyleCommentsSkipStream was/is a quick hack and does
>> not know/understand anything about strings.
>>
>>
> On 16 Jul 2015, at 21:28, Sven Van Caekenberghe wrote:
>
> Guille,
>
> I understand the problem.
>
> The reason is that STONCStyleCommentsSkipStream was/is a quick hack and does
> not know/understand anything about strings.
>
> It seems that the C preprocessor ignores comments in C strings
28 matches
Mail list logo
