Speaking of improving the VCS usage, how about tagging?
It would be nice if a tag is created for each dmd, phobos and druntime
repositories, sometimes I want to see what changed between a version and
another and it's not trivial to do so.
I know there is a changelog in the website, but I wa
On Tue, 01 Dec 2009 11:16:06 -0500, Leandro Lucarella
wrote:
Speaking of improving the VCS usage, how about tagging?
It would be nice if a tag is created for each dmd, phobos and druntime
repositories, sometimes I want to see what changed between a version and
another and it's not tr
On Tue, Dec 1, 2009 at 8:45 AM, Steven Schveighoffer
wrote:
> On Tue, 01 Dec 2009 11:16:06 -0500, Leandro Lucarella
> wrote:
>
>> Speaking of improving the VCS usage, how about tagging?
>>
>> It would be nice if a tag is created for each dmd, phobos and druntime
>&g
Leandro Lucarella Wrote:
> Speaking of improving the VCS usage, how about tagging?
An easy intermediate step would be to include the SVN revision numbers of
Phobos ad Druntime when a release is packaged. In fact, the makefiles could
probably dump this information somewhere and have it bu
On Tue, 01 Dec 2009 11:52:32 -0500, Sean Kelly
wrote:
Leandro Lucarella Wrote:
Speaking of improving the VCS usage, how about tagging?
An easy intermediate step would be to include the SVN revision numbers
of Phobos ad Druntime when a release is packaged. In fact, the
makefiles
Bill Baxter, el 1 de diciembre a las 08:53 me escribiste:
> On Tue, Dec 1, 2009 at 8:45 AM, Steven Schveighoffer
> wrote:
> > On Tue, 01 Dec 2009 11:16:06 -0500, Leandro Lucarella
> > wrote:
> >
> >> Speaking of improving the VCS usage, how about tagging?
>
Sean Kelly, el 1 de diciembre a las 11:52 me escribiste:
> Leandro Lucarella Wrote:
>
> > Speaking of improving the VCS usage, how about tagging?
>
> An easy intermediate step would be to include the SVN revision numbers
> of Phobos ad Druntime when a release is pa
On Tue, Dec 1, 2009 at 9:19 AM, Leandro Lucarella wrote:
> Sean Kelly, el 1 de diciembre a las 11:52 me escribiste:
>> Leandro Lucarella Wrote:
>>
>> > Speaking of improving the VCS usage, how about tagging?
>>
>> An easy intermediate step would be to in
Leandro Lucarella Wrote:
> Sean Kelly, el 1 de diciembre a las 11:52 me escribiste:
> > Leandro Lucarella Wrote:
> >
> > > Speaking of improving the VCS usage, how about tagging?
> >
> > An easy intermediate step would be to include the SVN revision numb
Steven Schveighoffer Wrote:
> On Tue, 01 Dec 2009 11:52:32 -0500, Sean Kelly
> wrote:
>
> > Leandro Lucarella Wrote:
> >
> >> Speaking of improving the VCS usage, how about tagging?
> >
> > An easy intermediate step would be to include the SVN revisio
On 01.12.2009 6:33, Bill Baxter wrote:
Perhaps Walter just doesn't really know what tags are or what they are good for.
I've always had the feeling that Walter doesn't actually use svn as a
tool for his work. He just checks in stuff when he's done. That would
explain why he doesn't add tags
Sean Kelly wrote:
> It's easier because it could be built into the Druntime/Phobos makefiles
> and not rely on a release script or manual effort to actually happen.
Are you saying that a SVN one-liner once per release requires too much
effort on Walter's side?
Apart from that, I don't quite see
This is a recently opened (not by me) enhancement request thread:
http://d.puremagic.com/issues/show_bug.cgi?id=6442
It proposes something that I remember was discussed and refused two times in
past: to require (but only optionally!) "ref" and "out" at the calling point,
as C#4 instead always re
One the main reasons c# has mandatory out and ref at call site is code
versioning. If some function took an argument by value but was changed
to take if by reference, without annotations compiler would treat this
as an error, preventing a potential bug.
So this feature has to be either mandato
Max Klyga:
> So this feature has to be either mandatory or not. Making it optional
> leads to confusion as Jonathan mentioned.
On this, what I have suggested it not the same thing that the original proposal
says. In the original proposal the "ref" and "out" are optional. In my
alternative pro
On 2011-08-07 20:42:30 +, bearophile said:
This is a recently opened (not by me) enhancement request thread:
http://d.puremagic.com/issues/show_bug.cgi?id=6442
It proposes something that I remember was discussed and refused two
times in past: to require (but only optionally!) "ref" and "o
Michel Fortin wrote:
> On 2011-08-07 20:42:30 +, bearophile said:
>
>> This is a recently opened (not by me) enhancement request thread:
>> http://d.puremagic.com/issues/show_bug.cgi?id=6442
>>
>> It proposes something that I remember was discussed and refused two
>> times in past: to require
bearophile wrote:
Max Klyga:
So this feature has to be either mandatory or not. Making it optional
leads to confusion as Jonathan mentioned.
On this, what I have suggested it not the same thing that the original proposal says. In the original proposal the
"ref" and "out" are optional. In my
Michel Fortin Wrote:
> I recently had to use getopt. You use it like that:
>
> bool option;
> int counter;
>
> getopt(args,
> "option|o", &option,
> "counter|c", &counter);
>
> The problem is that taking addresses of a stack variable is disabled in
bearophile Wrote:
> This is a recently opened (not by me) enhancement request thread:
> http://d.puremagic.com/issues/show_bug.cgi?id=6442
D is the language to save keystrokes. This proposal is plain invalid.
Though I think, `main` arguments should eliminated altogether and be accessed
statically.
const ReusableOpts opts = getopts();
const string[] args = mainArgs; // @property: parse args on demand, remove the
code from startup.
On Aug 9, 11 02:32, Kagamin wrote:
bearophile Wrote:
This is a recently opened (not by me) enhancement request thread:
http://d.puremagic.com/issues/show_bug.cgi?id=6442
D is the language to save keystrokes. This proposal is plain invalid.
I disagree. If you want to save keystrokes, use Per
> bearophile Wrote:
> > This is a recently opened (not by me) enhancement request thread:
> > http://d.puremagic.com/issues/show_bug.cgi?id=6442
>
> D is the language to save keystrokes. This proposal is plain invalid.
We're not going to reject a feature proposal simply because it involves more
I think we can use "auto ref".
2011/08/08 21:45 "Michel Fortin" :
> On 2011-08-07 20:42:30 +, bearophile said:
>
>> This is a recently opened (not by me) enhancement request thread:
>> http://d.puremagic.com/issues/show_bug.cgi?id=6442
>>
>> It proposes something that I remember was discussed
KennyTM~ Wrote:
> I disagree. If you want to save keystrokes, use Perl.
Perl is dynamically typed, right? D is statically typed, so it can statically
check most things like out variables won't overwrite const arguments.
FWIW, Google's C++ style guide explicitly requires passing pointers to
arguments (whenever possible) when they are to be modified or used as out
parameters, and passed by const& when they are not. This makes it more
obvious at the caller's end which parameters are going to be modified and
which one
Ziad Hatahet:
> FWIW, Google's C++ style guide explicitly requires passing pointers to
> arguments (whenever possible) when they are to be modified or used as out
> parameters, and passed by const& when they are not.
It's here:
http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml#Refere
On 2011-08-08 18:30:10 +, Kagamin said:
Michel Fortin Wrote:
I recently had to use getopt. You use it like that:
bool option;
int counter;
getopt(args,
"option|o", &option,
"counter|c", &counter);
The problem is that taking addres
28 matches
Mail list logo
