On Monday, 7 January 2019 at 14:25:26 UTC, H. S. Teoh wrote:
A text-based links browser with a focused use case sounds like
a far better idea. Though programs like elinks or pinfo may
have already have you beat on this front. :-D
elinks does an ok job on dpldocs (of course, I partially
On 1/4/19 7:16 PM, kdevel wrote:
On Friday, 4 January 2019 at 20:21:56 UTC, Steven Schveighoffer wrote:
missing in the source. But why is d a null reference in the first place?
Because when you dynamically cast one object or interface to another
object or interface, and that result is not
static foreach(k, p; AliasSeq!(this, s))
{{
p.foo(); // Fails even if this line is removed
}}
this not known at compile time. replace s with this and it works!
s is an argument which is also not known at compile
time(generally).
Should work with this.
Just "simplifying"
On Sun, Jan 06, 2019 at 03:11:48AM +, Adam D. Ruppe via Digitalmars-d-learn
wrote:
[...]
> http://arsdnet.net/arsd/dman.png
>
> But that's the result of about 5 mins of work... though I really like
> my hyperlinks and actually kinda prefer the browser for that reason
> (tho making a custom
On Monday, 7 January 2019 at 16:16:57 UTC, Michelle Long wrote:
On Monday, 7 January 2019 at 16:01:50 UTC, Michelle Long wrote:
static foreach(k, p; AliasSeq!(this, s))
{{
p.foo(); // Fails even if this line is removed
}}
this not known at compile time. replace s with this
On 1/7/19 11:16 AM, Michelle Long wrote:
On Monday, 7 January 2019 at 16:01:50 UTC, Michelle Long wrote:
static foreach(k, p; AliasSeq!(this, s))
{{
p.foo(); // Fails even if this line is removed
}}
this not known at compile time. replace s with this and it works! s is
an argument which
On Monday, 7 January 2019 at 16:31:49 UTC, Steven Schveighoffer
wrote:
On 1/7/19 11:16 AM, Michelle Long wrote:
On Monday, 7 January 2019 at 16:01:50 UTC, Michelle Long wrote:
[...]
static foreach(k, p; AliasSeq!(Alias!this, s))
{{
p.foo(); // Fails even if this line is removed
}}
To
On Monday, 7 January 2019 at 14:39:07 UTC, Per Nordlöw wrote:
What's the preferred way of doing bitwise rotate of an integral
value in D?
Are there intrinsics for bitwise rotation available in LDC?
I just found this
ulong rotateLeft(ulong x, ubyte bits)
{
return (x << bits)
On Monday, 7 January 2019 at 14:53:26 UTC, Alex wrote:
There are
https://dlang.org/phobos/core_bitop.html#.rol
and
https://dlang.org/phobos/core_bitop.html#.ror
But it seems the implementation is like yours.
Ahh, missed that. Thanks.
On 1/7/19 10:10 AM, Per Nordlöw wrote:
On Monday, 7 January 2019 at 14:53:26 UTC, Alex wrote:
There are
https://dlang.org/phobos/core_bitop.html#.rol
and
https://dlang.org/phobos/core_bitop.html#.ror
But it seems the implementation is like yours.
Ahh, missed that. Thanks.
Use the
On Monday, 7 January 2019 at 16:29:25 UTC, Alex wrote:
On Monday, 7 January 2019 at 16:16:57 UTC, Michelle Long wrote:
On Monday, 7 January 2019 at 16:01:50 UTC, Michelle Long wrote:
static foreach(k, p; AliasSeq!(this, s))
{{
p.foo(); // Fails even if this line is removed
What's the preferred way of doing bitwise rotate of an integral
value in D?
Are there intrinsics for bitwise rotation available in LDC?
On Monday, 7 January 2019 at 14:43:29 UTC, Per Nordlöw wrote:
On Monday, 7 January 2019 at 14:39:07 UTC, Per Nordlöw wrote:
What's the preferred way of doing bitwise rotate of an
integral value in D?
Are there intrinsics for bitwise rotation available in LDC?
I just found this
ulong
On Monday, 7 January 2019 at 09:57:45 UTC, Daniel Kozak wrote:
I would go with std.conv.to or std.conv.text :)
The reason for not using std.conv.to is to prevent the extra
allocation needed in code such as
sink.put(someIntegral.to!string)
instead of something like
On Monday, 7 January 2019 at 12:19:57 UTC, Andre Pany wrote:
Hi,
I call a C function from a dll (SO on linux). While the
following code works
fine for DMD on windows, there are strange errors for LDC on
windows. Also the equivalent code does not work for DMD/LDC on
linux.
(When calling other
On Sunday, 6 January 2019 at 21:53:31 UTC, Per Nordlöw wrote:
When converting a single integer to a string is `formatValue`
preferred over `formattedWrite` in terms of compilation and
run-time performance?
I've written my own itos function because using std.conv was too
expensive.
see
Hi,
I call a C function from a dll (SO on linux). While the following
code works
fine for DMD on windows, there are strange errors for LDC on
windows. Also the equivalent code does not work for DMD/LDC on
linux.
(When calling other functions from the dll and passing the model
reference, this
On Monday, 7 January 2019 at 13:01:57 UTC, Stefan Koch wrote:
On Monday, 7 January 2019 at 12:19:57 UTC, Andre Pany wrote:
Hi,
I call a C function from a dll (SO on linux). While the
following code works
fine for DMD on windows, there are strange errors for LDC on
windows. Also the
On Sunday, 6 January 2019 at 21:53:31 UTC, Per Nordlöw wrote:
When converting a single integer to a string is `formatValue`
preferred over `formattedWrite` in terms of compilation and
run-time performance?
Also, if you do not need to write to a stream or a range and just
need the value,
On 2019-01-05 16:17, Mike Parker wrote:
What I do is use `dub add-local /path/to/lib 0.0.1` and use that
explicit version for development. That way, whatever repository branch
is currently active in that directory becomes version 0.0.1 and I can
make use of any changes.
The problem with
I am learning D. I was working on Project Euler #199 (possible
spoilers) and got some unexpected results. It's probably a
stupid mistake but I can't see it.
Here is an edited function from my program:
auto radius(const double r1, const double r2, const double r3) {
auto const k1 = 1/r1;
On Monday, 7 January 2019 at 18:56:17 UTC, H. S. Teoh wrote:
On Mon, Jan 07, 2019 at 06:42:13PM +, Patrick Schluter via
Digitalmars-d-learn wrote:
On Monday, 7 January 2019 at 17:23:19 UTC, Michelle Long wrote:
> Is there any direct way to convert a signed nibble in to a
> signed byte with
On Mon, Jan 07, 2019 at 07:57:14PM +, Joseph Malle via Digitalmars-d-learn
wrote:
[...]
> auto radius(const double r1, const double r2, const double r3) {
> auto const k1 = 1/r1;
> auto const k2 = 1/r2;
> auto const k3 = 1/r3;
> writeln();
> writeln("1 ", [k1, k2, k3]);
>
On Mon, Jan 07, 2019 at 06:42:13PM +, Patrick Schluter via
Digitalmars-d-learn wrote:
> On Monday, 7 January 2019 at 17:23:19 UTC, Michelle Long wrote:
> > Is there any direct way to convert a signed nibble in to a signed
> > byte with the same absolute value? Obviously I can do some bit
> >
On Monday, 7 January 2019 at 18:42:13 UTC, Patrick Schluter wrote:
byte b = nibble | ((nibble & 0x40)?0xF0:0);
don't you mean & 0x80 ?
On Monday, 7 January 2019 at 20:28:21 UTC, H. S. Teoh wrote:
On Mon, Jan 07, 2019 at 08:06:17PM +, Patrick Schluter via
Digitalmars-d-learn wrote:
On Monday, 7 January 2019 at 18:56:17 UTC, H. S. Teoh wrote:
> On Mon, Jan 07, 2019 at 06:42:13PM +, Patrick Schluter
> via
On Mon, Jan 07, 2019 at 05:23:19PM +, Michelle Long via Digitalmars-d-learn
wrote:
> Is there any direct way to convert a signed nibble in to a signed byte
> with the same absolute value? Obviously I can do some bit comparisons
> but just curious if there is a very quick way.
Assuming you
On Monday, 7 January 2019 at 18:47:04 UTC, Adam D. Ruppe wrote:
On Monday, 7 January 2019 at 18:42:13 UTC, Patrick Schluter
wrote:
byte b = nibble | ((nibble & 0x40)?0xF0:0);
don't you mean & 0x80 ?
He asked for signed nybble. So mine is wrong and yours also :-)
It's obviously 0x08 for the
On 1/7/19 12:20 AM, Jonathan M Davis wrote:
On Sunday, January 6, 2019 11:38:44 AM MST Benjamin Thaut via Digitalmars-d-
learn wrote:
Today I found a bug in my D code.
import std.stdio;
// Type your code here, or load an example.
void grow()
{
writeln("grow");
}
void someFunc(bool
Is there any direct way to convert a signed nibble in to a signed
byte with the same absolute value? Obviously I can do some bit
comparisons but just curious if there is a very quick way.
On Monday, 7 January 2019 at 17:23:19 UTC, Michelle Long wrote:
Is there any direct way to convert a signed nibble in to a
signed byte with the same absolute value? Obviously I can do
some bit comparisons but just curious if there is a very quick
way.
byte b = nibble | ((nibble &
On Mon, Jan 07, 2019 at 08:06:17PM +, Patrick Schluter via
Digitalmars-d-learn wrote:
> On Monday, 7 January 2019 at 18:56:17 UTC, H. S. Teoh wrote:
> > On Mon, Jan 07, 2019 at 06:42:13PM +, Patrick Schluter via
> > Digitalmars-d-learn wrote:
[...]
> > > byte b = nibble | ((nibble &
Will AtoX replace SWIFT?
Society for Worldwide Interbank Financial Telecommunication
(SWIFT) is a non-profitable international and cooperative
organization between international bank that provides fast,
accurate and excellent services to international financial
services. It operates a
On Mon, Jan 07, 2019 at 08:41:32PM +, Patrick Schluter via
Digitalmars-d-learn wrote:
> On Monday, 7 January 2019 at 20:28:21 UTC, H. S. Teoh wrote:
> > On Mon, Jan 07, 2019 at 08:06:17PM +, Patrick Schluter via
> > Digitalmars-d-learn wrote:
[...]
> > > Up to 32 bit processors, shifting
On Mon, Jan 07, 2019 at 11:13:37PM +, Guillaume Piolat via
Digitalmars-d-learn wrote:
> On Monday, 7 January 2019 at 14:39:07 UTC, Per Nordlöw wrote:
> > What's the preferred way of doing bitwise rotate of an integral
> > value in D?
> >
> > Are there intrinsics for bitwise rotation
On Monday, 7 January 2019 at 14:39:07 UTC, Per Nordlöw wrote:
What's the preferred way of doing bitwise rotate of an integral
value in D?
Are there intrinsics for bitwise rotation available in LDC?
Turns out you don't need any:
https://d.godbolt.org/z/C_Sk_-
Generates ROL instruction.
On Monday, 7 January 2019 at 20:18:28 UTC, H. S. Teoh wrote:
Either there's memory corruption somewhere, or there's a
codegen bug in the compiler.
I think that must be it. I ran it with ldc instead of dmd and it
worked fine (solved the original problem! woohoo).
Or the compiler somehow is
On Mon, Jan 07, 2019 at 09:42:42PM +, Joseph Malle via Digitalmars-d-learn
wrote:
> On Monday, 7 January 2019 at 20:18:28 UTC, H. S. Teoh wrote:
> > Either there's memory corruption somewhere, or there's a codegen bug
> > in the compiler.
>
> I think that must be it. I ran it with ldc
38 matches
Mail list logo
