On Thursday, 22 March 2018 at 09:55:44 UTC, Russel Winder wrote:
I am guessing you mean against DStep rather than D :-)
Yes :)
Though clearly T and I would prefer version not to be a D
keyword.
I suspect I have seen one place where DStep has turned version
into version_ where version was
On Wednesday, 21 March 2018 at 19:41:39 UTC, H. S. Teoh wrote:
version(all) { ... }
version(none) { ... }
version(Posix) { ... }
version(Windows) { ... }
But yeah, using "version" for this purpose makes the very
common identifier "version" unavailable for use.
On Wed, 2018-03-21 at 22:18 +0100, Jacob Carlborg via Digitalmars-d-learn
wrote:
> On 2018-03-21 20:30, Russel Winder wrote:
>
> > Thanks to Adam and Ali, it was clear and obvious.
>
> Please report and issue so it's not forgotten.
I am guessing you mean against DStep rather than D :-)
Though
On 2018-03-21 20:30, Russel Winder wrote:
Thanks to Adam and Ali, it was clear and obvious.
Please report and issue so it's not forgotten.
--
/Jacob Carlborg
On Wed, Mar 21, 2018 at 07:30:28PM +, Russel Winder via Digitalmars-d-learn
wrote:
[...]
> But :-(
>
> Why does version have to be a keyword?
[...]
version(all) { ... }
version(none) { ... }
version(Posix) { ... }
version(Windows) { ... }
But yeah, using
On Wed, 2018-03-21 at 18:11 +, Adam D. Ruppe via Digitalmars-d-
learn wrote:
> On Wednesday, 21 March 2018 at 18:00:38 UTC, Russel Winder wrote:
> > ubyte, "version", 5,
>
>
> version is a D keyword, so I would suggest trying "version_"
> there instead and see if it works. (I'm
On 03/21/2018 11:00 AM, Russel Winder wrote:
> The code I am playing with generated by DStep involves lots of lots of
> structs with mixin bitfields. All of them seem to compile file, except
> one. How is it that:
>
> mixin(bitfields!(
> ubyte, "current_next", 1,
> ubyte,
On Wednesday, 21 March 2018 at 18:00:38 UTC, Russel Winder wrote:
ubyte, "version", 5,
version is a D keyword, so I would suggest trying "version_"
there instead and see if it works. (I'm guessing btw, the error
message was way to long and illegible, but this is an easy first
guess
The code I am playing with generated by DStep involves lots of lots of
structs with mixin bitfields. All of them seem to compile file, except
one. How is it that:
mixin(bitfields!(
ubyte, "current_next", 1,
ubyte, "version", 5,
ubyte, "one2", 2)); /* TS ID */
can
