Re: It's alive! D building D building D, all on Android

Quite nice!

Re: Live streaming of DConf 2016: confirmed

Joakim writes: >>> Sound doesn't work in the official Ustream Android app either for >>> the Dconf stream, as I noted. My guess would be that the HTML5 >>> player and the Android app try to use whatever audio codecs are >>> built into Android, instead of the app using its

Re: Live streaming of DConf 2016: confirmed

Joakim writes: > On Wednesday, 4 May 2016 at 09:13:12 UTC, Dženis Kiderič wrote: >> On Wednesday, 4 May 2016 at 09:04:38 UTC, Dicebot wrote: >>> On Wednesday, 4 May 2016 at 08:33:47 UTC, Joakim wrote: There appears to be a problem with the sound on Ustream with

Re: LDC 1.0.0-beta1 has been released! Please help testing!

Kai Nacke writes: > Hi everyone, > > LDC 1.0.0-beta1, the LLVM-based D compiler, is available for download! > This BETA release is based on the 2.070.2 frontend and standard > library and supports LLVM 3.5-3.8. > > The 1.0 release will be a major milestone. Please help testing

Re: Using D in Android App

Justice writes: > On Saturday, 16 April 2016 at 04:04:24 UTC, Justice wrote: >> Is it difficult to create a D business like app and connect it to >> android through java for the interface? >> >> I'd rather create all the complex stuff in D and either use it >> natively

cast double to long for value greater than long.max

This revolves around a dmd test which fails on ARM: https://github.com/D-Programming-Language/dmd/blob/master/test/runnable/constfold.d#L321 int bug7(int x) { return x; } static assert(!is(typeof(bug7(cast(long)3.256679e30; Is it a valid test? Or specifically, is a cast from double to

Re: TECO - Inspiration for the D programming language

Walter Bright writes: > > https://www.reddit.com/r/programming/comments/4e07lo/last_night_in_a_fit_of_boredom_far_away_from_my/d1x5rl7 I am tempted to try it on my TOPS-10 (PDP-10) account at LCM. I believe TECO is installed. -- Dan

Re: D could catch this wave: web assembly

CraigDillabaugh writes: > On Monday, 14 March 2016 at 15:53:39 UTC, Joakim wrote: >> On Monday, 14 March 2016 at 15:14:17 UTC, CraigDillabaugh wrote: >> >> I'm not qualified to mentor a WebAssembly port, as I'm not versed on >> compilers or IR. Dan would probably be

Tease: Empire on Pi

This is a tease because there is nothing you can download and I am occupied with other stuff at the moment, but... While improving LDC linux ARM support, I've been using an original Pi to debug, test the changes, and it is all in good shape. Now, back in 2012 I changed the Windows D version of

Re: LDC 0.17.0-beta1 has been released!

Adrian Matoga writes: > On Thursday, 14 January 2016 at 20:33:30 UTC, Kai Nacke wrote: >> LDC 0.17.0-beta1, the LLVM-based D compiler, is available for >> download! >> This release is based on the 2.068.2 frontend and standard library >> and supports LLVM 3.5-3.7. > >

Re: LDC 0.17.0-beta1 has been released!

Manu via Digitalmars-d-announce writes: > > Love your work guys! Thanks for keeping at it. > > One question though, what's the plan for moving to DMD latest? Both > LDC and GDC seem to be quite behind at the moment. > My current project is depending on

Re: D runs on watchOS! and on Android Wear too!

Laeeth Isharc writes: > I can confirm that D also runs on Android Wear (Huawei watch) and > passes all unit tests. Forgive the slight hijack, but I mention this > here as people might see this thread and not the obscure one where I > reported this previously. I

Re: Better watch out! D runs on watchOS!

Joakim writes: > On Thursday, 31 December 2015 at 00:11:34 UTC, Dan Olson wrote: >> On Wednesday, 30 December 2015 at 23:11:06 UTC, Joakim wrote: >>> That sounds like this issue I ran into with ARM EH: >>> >>>

Re: GC configuration docs

Rainer Schuetze writes: > On 05.01.2016 01:39, Dan Olson wrote: >> I haven't played with any of the new GC configuration options introduced >> in 2.067, but now need to. An application on watchOS currently has >> about 30 MB of RAM. Is there any more documentation than the

Re: What are you planning for 2016?

Ola Fosheim Grøstad writes: > 5. run D apps on mobile? 1) I am involved in recreational windsurf races and pretty much everyone carries a mobile phone to record GPS tracks. I though it would be fun to create an app to manage the races, track finishing

Re: Better watch out! D runs on watchOS!

Joakim writes: > On Monday, 4 January 2016 at 09:26:39 UTC, Dan Olson wrote: >> Joakim writes: >> >>> On Thursday, 31 December 2015 at 00:11:34 UTC, Dan Olson wrote: [...] >>> >>> Sounds good, submit a PR and let's get it in. >> >> Was planning to

Re: Better watch out! D runs on watchOS!

Joakim writes: > On Thursday, 31 December 2015 at 00:11:34 UTC, Dan Olson wrote: >> On Wednesday, 30 December 2015 at 23:11:06 UTC, Joakim wrote: >>> That sounds like this issue I ran into with ARM EH: >>> >>>

Re: DMD now does Dwarf style exception handling!

Walter Bright writes: > What I've been working on for the last month or so. > > https://github.com/D-Programming-Language/dmd/pull/5324 > > For Linux 64 anyway. Anyone who wants to do PRs to extend it to Linux > 32, OSX and FreeBSD, feel free! Unfortunately, this is

Re: Better watch out! D runs on watchOS!

Joakim writes: > On Monday, 4 January 2016 at 09:26:39 UTC, Dan Olson wrote: >> Joakim writes: > >> The bug is a bad stack pointer which blows up when the last unittest >> returns. This unittest has all the right conditions to generate >> stack

Re: Better watch out! D runs on watchOS!

Jacob Carlborg writes: > On 2015-12-30 08:02, Dan Olson wrote: > >> I know some of it from hacking dyld for iOS, but not all. How does this >> fit in with "Plan B.2"? > > If you need to figure out how TLS works, I can give you some help, > that's all I'm saying :) Oh, good.

Re: Better watch out! D runs on watchOS!

On Wednesday, 30 December 2015 at 23:11:06 UTC, Joakim wrote: That sounds like this issue I ran into with ARM EH: https://github.com/ldc-developers/ldc/issues/489#issuecomment-143560075 I was able to work around it by disabling the mentioned llvm optimization pass:

Re: Better watch out! D runs on watchOS!

Jacob Carlborg writes: > On 2015-12-28 20:02, Dan Olson wrote: > >> That is Plan B.2 > > I'm working on implementing native TLS for OS X in DMD. I think I've > figured out how everything works. Unless you already know how it > works, I could tell you what I have figured out. I know

Re: Better watch out! D runs on watchOS!

Joakim writes: > > I don't understand how the bitcode requirement works on your own > device: I thought that was for an Apple-submitted app that they then > compiled to binary themselves? Do you have to go through the same > process even for test apps, ie no sideloading? Or

Re: Better watch out! D runs on watchOS!

Jacob Carlborg writes: > > Would it be possible to bypass LLVM and do the thread local specific > parts in LDC? That is Plan B.2

Re: Better watch out! D runs on watchOS!

Joakim writes: > > Thanks for the detailed answer; I'm sure this will now become the > definitive answer online. I've gone googling for technical info only > to sometimes be directed back to a post in these D forums. :) Me too! Its very funny when that happens. > Time to

Better watch out! D runs on watchOS!

A little progress report. More to come later when I get something pushed to github. I bought a returned Apple Watch yesterday at discount for $223.99 US and tried to see how much of D would work on it using my iOS fork of LDC. There were a few bumps, like dealing with embedded bitcode (a watchOS

Re: LDC 0.17.0-alpha1 has been released!

Kai Nacke writes: > Hi everyone, > > LDC 0.17.0-alpha1, the LLVM-based D compiler, is available for > download! > This release is based on the 2.068.2 frontend and standard library and > supports LLVM 3.5-3.7. > > Don't miss to check if your preferred system is supported by this

Re: Catching C++ std::exception in D

David Nadlinger writes: > On Friday, 13 November 2015 at 18:40:06 UTC, Iain Buclaw wrote: >> There may be a few other holes between how Fibers and EH interact. >> >> https://github.com/D-Programming-Language/druntime/commit/f6633abb43ea1f2464d3a772b8f8fe78216ffd8e > > The

Re: Catching C++ std::exception in D

Dan Olson writes: > Johannes Pfau writes: > >> Am Thu, 12 Nov 2015 09:59:14 -0800 >> schrieb Dan Olson : >> >>> Johannes Pfau writes: >>> > To expand on this: I think we'd prefer one __d_personality_v0 which >>> > is

Re: Catching C++ std::exception in D

Johannes Pfau writes: > Am Thu, 12 Nov 2015 09:59:14 -0800 > schrieb Dan Olson : > >> Johannes Pfau writes: >> > To expand on this: I think we'd prefer one __d_personality_v0 which >> > is implemented in upstream druntime and identical

Re: Catching C++ std::exception in D

Johannes Pfau writes: > To expand on this: I think we'd prefer one __d_personality_v0 which is > implemented in upstream druntime and identical for all compilers. Speacking of upstream support. GDC support SjLj exceptions. In 2.067, it became obvious that Fiber needed

Re: iOS LDC 0.16.1 (2.067.1) binaries available

Joakim writes: > On Saturday, 7 November 2015 at 19:20:02 UTC, Dan Olson wrote: >> Dan Olson writes: >> >>> Joakim writes: btw, std.internal.math.gammafunction hasn't given me a problem since 2.067.1, the Win64 guys fixed

Re: iOS LDC 0.16.1 (2.067.1) binaries available

Dan Olson writes: > Joakim writes: >> btw, std.internal.math.gammafunction hasn't given me a problem since >> 2.067.1, the Win64 guys fixed it. 2.068 added a function that needs a >> CTFE-able 64-bit log2, but other than that, it just works now. You >>

Re: iOS LDC 0.16.1 (2.067.1) binaries available

Joakim writes: > On Saturday, 7 November 2015 at 20:34:06 UTC, Dan Olson wrote: >> Joakim writes: >>> Hmm, that's strange, this commit didn't fix the 64-bit issues for >>> you? I believe it fixed them for me on Android/ARM: >>> >>>

Re: iOS LDC 0.16.1 (2.067.1) binaries available

Joakim writes: > btw, std.internal.math.gammafunction hasn't given me a problem since > 2.067.1, the Win64 guys fixed it. 2.068 added a function that needs a > CTFE-able 64-bit log2, but other than that, it just works now. You > may want to revert your patch for that module

Re: LDC 0.17.0 alpha cross-compiler for Android/ARM, D 2.068.2

Go mobile!

Re: iOS LDC 0.16.1 (2.067.1) binaries available

Just a few more notes: Dan Olson writes: > Feedback appreciated, especially since iOS support may get into official > LDC sometime soon. This is a good time to voice an opinion on the > approach. Just noticed that tvOS and watchOS are now present in LLVM, so I think support

Re: iOS LDC 0.16.1 (2.067.1) binaries available

Joakim writes: > Great, your last announcement was linked in reddit comments about the > 2.069 release, when asked about iOS support. > > On Thursday, 5 November 2015 at 08:05:39 UTC, Dan Olson wrote: >> Just noticed that tvOS and watchOS are now present in LLVM, so I >>

iOS LDC 0.16.1 (2.067.1) binaries available

This is another set of binaries and universal libs for the experimental LDC iOS cross-compiler. It is now based on LDC 0.16.1 (2.067.1) and LLVM 3.6.2. https://github.com/smolt/ldc-iphone-dev/releases/tag/ios-0.16.1-151104 Feedback appreciated, especially since iOS support may get into official

Re: Mobile support

Vladimir Panteleev writes: > On Monday, 26 October 2015 at 05:34:05 UTC, Dan Olson wrote: >> I think it makes sense to add a link to the LDC iOS releases in >> http://wiki.dlang.org/Compilers. Perhaps a row for iOS in table >> "Package and/or binary availability,

Re: Mobile support

Andrei Alexandrescu writes: > On 10/18/15 7:55 AM, Joakim wrote: >> Now, the download page has not traditionally listed alphas and betas. >> But the importance of mobile is so high that I think it is worth it to >> do so, with the appropriate cautions about alpha

Re: LDC iOS cross-compiler with arm64

Jacob Carlborg writes: > On 2015-10-24 12:01, Suliman wrote: > >> Would it be hard to add Windows/Linux host available? Would it be hard >> to develop iOS apps on Windows in comparison of using MacOSX? > > It depends on what you mean. Microsoft already supports developing iOS > apps

Re: LDC iOS cross-compiler with arm64

extrawurst writes: > On Saturday, 24 October 2015 at 07:07:18 UTC, Dan Olson wrote: >> This is another set of binaries and universal libs for the >> experimental LDC iOS cross-compiler. It is now based on LDC 0.15.2 >> (2.066.1) and LLVM 3.6.1. >> >> [...] > > Cool work!

LDC iOS cross-compiler with arm64

This is another set of binaries and universal libs for the experimental LDC iOS cross-compiler. It is now based on LDC 0.15.2 (2.066.1) and LLVM 3.6.1. https://github.com/smolt/ldc-iphone-dev/releases/tag/ios-0.15.2-151023 What's new? - arm64 for iOS 64-bit devices - C ABI compatibility

Re: Seattle D meetup

Colden Cullen coldencul...@gmail.com writes: On Sunday, 2 August 2015 at 22:53:00 UTC, Walter Bright wrote: Seeing the threads on London, Silicon Valley and Berlin meetups, is there any interest for a Seattle one? Yes please! Myself and a good portion of the Dash[1] team are in Seattle now,

Re: D for Android

Joakim dl...@joakim.fea.st writes: Some good news, I've made progress on the port to Android/ARM, using ldc's 2.067 branch. Currently, all 46 modules in druntime and 85 of 88 modules in phobos pass their tests (I had to comment out a few tests across four modules) when run on the

Re: Firs step of D/Objective-C merged

Very good news!

Re: LDC for iOS prebuilt binaries

Jack Stouffer j...@jackstouffer.com writes: Does this have any way to call the iOS Obj-C libraries for UI rendering and the like? Or is that a separate project? It is a separate project and is gradually getting pulled into DMD: http://forum.dlang.org/post/mnm1sf$kp8$1...@digitalmars.com For

Re: LDC for iOS prebuilt binaries

Manu via Digitalmars-d-announce digitalmars-d-announce@puremagic.com writes: Possible to make cross compilers for other hosts? Who uses a mac? ;) Hi Manu - I wish I knew the answer. I assume you are thinking Windows. I just looked at some stackoverflow answers, specifically at Xamarin.iOS for

LDC for iOS prebuilt binaries

I've made a set of binaries and universal libs for the LDC iOS cross-compiler. It is based on LDC 0.15.1 (2.066) and LLVM 3.5.1. https://github.com/smolt/ldc-iphone-dev/releases/tag/ios-0.15.1-150708 Only 32-bit devices currently; arm64 work starts next month when I acquire an iPhone 6. The

Re: Any D plugins for recent Xcode?

Michel Fortin michel.for...@michelf.ca writes: On 2015-04-19 00:28:14 +, Michel Fortin michel.for...@michelf.ca said: It's undocumented API, and they sometime change it although not that much. Xcode 4 broke the plugin and I didn't put much effort into figuring out what was wrong. Feel

Re: Any D plugins for recent Xcode?

Jacob Carlborg d...@me.com writes: On 2015-07-09 10:15, Dan Olson wrote: I started trying to update d-for-xcode, and although the plugin is still incompatible with Xcode 6 Xcode 7 should be the new target ;) It sometimes feels like running to catch a moving train, and stumbling just before

Re: D on Windows Phone

bitwise bitwise@gmail.com writes: On Tue, 30 Jun 2015 16:09:19 -0400, Jacob Carlborg d...@me.com wrote: On 30/06/15 18:29, Dan Olson wrote: Not to my knowledge, but please do try. The D iOS toolchain built by [1] only creates the armv7 libraries, but I have all the pieces staged to

Re: D on Windows Phone

bitwise bitwise@gmail.com writes: On Tue, 30 Jun 2015 12:29:17 -0400, Dan Olson go...@comcast.net wrote: bitwise bitwise@gmail.com writes: Has anyone tried to submit an app for iOS with D code in it yet? I'm going to be putting out a game in the next little while, so I was thinking

Re: D on Windows Phone

bitwise bitwise@gmail.com writes: Has anyone tried to submit an app for iOS with D code in it yet? I'm going to be putting out a game in the next little while, so I was thinking about sticking a D plugin in it to see if it raised any eyebrows. Bit Not to my knowledge, but please do

std.math.isIdentical and NaN

Docs for isIdentical say: Same as ==, except that positive and negative zero are not identical, and two NANs are identical if they have the same 'payload'. However, it returns false for NaN's with different signbits but same payload. Should this be the case? Ran into this because

Re: std.math.isIdentical and NaN

Jonathan M Davis jmdavisp...@gmx.com writes: On Monday, 22 June 2015 at 08:10:20 UTC, Dan Olson wrote: Docs for isIdentical say: Same as ==, except that positive and negative zero are not identical, and two NANs are identical if they have the same 'payload'. However, it returns

You too can work on D for iOS

Looks like there is no membership fee to build and install your own iOS apps with Xcode now. As usual, you still need a Mac to run Xcode. http://9to5mac.com/2015/06/10/xcode-7-allows-anyone-to-download-build-and-sideload-ios-apps-for-free/ -- Dan

Re: Lets talk about fibers

Ola Fosheim Grøstad\ ola.fosheim.grostad+dl...@gmail.com writes: No, there were no performance related reasons, only TLS (which is a questionable feature to begin with). On TLS and migrating Fibers - these were posted elsewhere, and want to make sure that when you read TLS Fiber problem here,

Re: Lets talk about fibers

Dmitry Olshansky dmitry.o...@gmail.com writes: On 03-Jun-2015 21:34, Liran Zvibel wrote: Hi, [snip] There are two main reasons why it does not make sense to move fibers between threads: For me language being TLS by default is enough to not even try this madness. If we allow moves a

Re: dmd makes D appear slow

ketmar ket...@ketmar.no-ip.org writes: yes, i remember lightning fast compile times with turbo pascal. yet the code it produced was really awful: it was even unable to fold constants sometimes! I remember it being in a single DOS .COM (was it TURBO.COM?) only about 40k which included the

Re: Uphill

Dan Olson go...@comcast.net writes: Stringify - here I want to rapidly prototype code with syscalls that need return values checked, and get nice output when they fails. My C++ template skills are weak and was unable to come up with an equivalent replacement. Is this a way? Meant Is there a

Re: Uphill

Ola Fosheim Grøstad\ ola.fosheim.grostad+dl...@gmail.com writes: On Monday, 1 June 2015 at 16:09:34 UTC, Dan Olson wrote: Timely! I and stack overflow struggled for a couple hours to find an equivalent C++ template for something that was straightforward with a couple macros. …but without

Re: Why aren't you using D at work?

Jacob Carlborg d...@me.com writes: On 2015-06-01 18:38, Dan Olson wrote: Yeah, we need to work on getting iOS support into LDC main offering. For now there is a stumbling block (at least perceived by me) of requiring a patched LLVM to support TLS on iOS. How you tried contributing that

Re: DConf 2015 has ended. See you in Berlin at DConf 2016!

Steven Schveighoffer schvei...@yahoo.com writes: On 6/1/15 11:40 AM, Dan Olson wrote: Dicebot pub...@dicebot.lv writes: - Moving fibers between threads (though there is some hope that Liran managed to convince Walter it is a bad idea) I am interesting in this one. What was the decision,

Re: Why aren't you using D at work?

Joakim dl...@joakim.fea.st writes: On Thursday, 28 May 2015 at 14:38:51 UTC, Manu wrote: I often wonder if others share the importance of mobile cross-compilers? I wonder that sometimes too, considering it's only two people working on them. They seem to be getting lots of love recently,

Re: Why aren't you using D at work?

Chris wend...@tcd.ie writes: 2. [high priority] Uncertainty regarding ARM (iOS/Android). Deal breaker, show stopper. Was worrying a few years ago, but is just bad now in 2015. It is a little better now :-) Maybe you can help Chris. I don't develop for mobile so I don't know that dev

Re: Uphill

Atila Neves atila.ne...@gmail.com writes: On Sunday, 31 May 2015 at 09:13:33 UTC, Ola Fosheim Grøstad wrote: On Sunday, 31 May 2015 at 08:51:00 UTC, Atila Neves wrote: While C++ programmers should try and avoid the preprocessor as much as possible, sometimes it just isn't possible to do so.

Re: DConf 2015 has ended. See you in Berlin at DConf 2016!

Dicebot pub...@dicebot.lv writes: - Moving fibers between threads (though there is some hope that Liran managed to convince Walter it is a bad idea) I am interesting in this one. What was the decision, that Fibers should or should not be allowed to migrate between threads? Is the discussion

Re: Why aren't you using D at work?

Manu via Digitalmars-d digitalmars-d@puremagic.com writes: On 1 June 2015 at 16:50, Dan Olson via Digitalmars-d And for iOS - https://github.com/smolt/ldc-iphone-dev I was hoping others would try out this ldc for iOS and give feedback, suggest where to focus next, but nothing so far. It does

Re: D for Android

Joakim dl...@joakim.fea.st writes: I just checked last week and the recent Android NDK's gcc has emulated TLS enabled by default, while the same C/C++ source employing TLS __thread and compiled with the NDK's clang will segfault because it doesn't have emulated TLS. Emulated TLS wasn't added

Re: D for Android

Joakim dl...@joakim.fea.st writes: Around 15 of 71 phobos modules' tests fail somewhere, most likely related to long double issues that either need to be backported, as git master for ldc is still using a year-old druntime/phobos that doesn't have some subsequent Android PRs, or fixed, but I

Re: RFC: Pay-as-you-go, Portable D Runtime for Microcontrollers (and maybe more)

Mike n...@none.com writes: I've gotten even further thanks to everyone's help, but LDC is still giving me a little grief. Take a look at these undefined references (abbreviated for this forum): (_D10TypeInfo_l6__vtblZ+0x8): undef ref `_D6object8TypeInfo8toStringMxFNaNbNfZAya' -- snip --

Re: RFC: Pay-as-you-go, Portable D Runtime for Microcontrollers (and maybe more)

Mike n...@none.com writes: That did it! But I thought defaultLib= did the same thing. Anyway, Thanks for all your help, Dan. I now have support for all 3 compilers porting to 2 different platforms (one bare metal microcontroller, one modern OS). It can't do anything more than Hello,

Re: RFC: Pay-as-you-go, Portable D Runtime for Microcontrollers (and maybe more)

The progress here is nice. I'd like to do similar stuff with LDC but have a couple other projects to finish up first. More thoughts on supporting systems without threads: Mike n...@none.com writes: On Tuesday, 5 May 2015 at 17:27:05 UTC, Johannes Pfau wrote: I'm not really sure about this.

Re: RFC: Pay-as-you-go, Portable D Runtime for Microcontrollers (and maybe more)

Mike n...@none.com writes: On Tuesday, 5 May 2015 at 06:39:42 UTC, Dan Olson wrote: LDC Folks: https://github.com/ldc-developers/ldc/issues/781 is currently preventing me from supporting LDC with this runtime. I looked at this and found a workaround and noted it in the above issue link.

Re: RFC: Pay-as-you-go, Portable D Runtime for Microcontrollers (and maybe more)

Iain Buclaw via Digitalmars-d digitalmars-d@puremagic.com writes: If the cost is too much (ie: there is no heap), then we should be able to stop emutls from kicking in by preventing the D frontend from returning true on isThreadLocal calls. Iain, I think something like this would be good in

Re: RFC: Pay-as-you-go, Portable D Runtime for Microcontrollers (and maybe more)

Mike n...@none.com writes: Read on GitHub: https://github.com/JinShil/minimal_druntime_experiment There was recently a discussion about how we could create a portable, pay-as-you-go, D runtime to help bring the promise of D to free-standing platforms and devices with tight resource

Re: [Hackathon] ARM Cortex-M LCD Demo

Jeremiah DeHaan dehaan.jerem...@gmail.com writes: On Friday, 1 May 2015 at 15:37:09 UTC, ketmar wrote: On Fri, 01 May 2015 15:30:21 +, Mike wrote: I know, random rectangles on a screen is not all that remarkable, they ARE remarkable! I agree. This is fantastic work! I am so excited to

Re: Is this expected? default to public members in private class

ketmar ket...@ketmar.no-ip.org writes: On Sun, 03 May 2015 18:07:20 -0700, Dan Olson wrote: It seems a private class or struct defaults to public members. Just curious if this is intended. I would have expected private all the way down unless overriden. i bet it is intended. protection

Is this expected? default to public members in private class

It seems a private class or struct defaults to public members. Just curious if this is intended. I would have expected private all the way down unless overriden. --- plugh.d module plugh; auto makeFoo() {return new Foo;} private: class Foo { void maybepriv() {} private void priv() {}

Re: Weird OSX issue

Jacob Carlborg d...@me.com writes: On 2015-04-24 20:37, Steven Schveighoffer wrote: So am I going crazy? Or is dmd doing things differently depending on where its environment is? Any compiler gurus out there understand why the symbol is different? I don't want to file a bug with this,

Re: std.json questions

tired_eyes pastuho...@gmail.com writes: First issue: what is the proper (idiomatic) way to conver JSONValue to the proper types? Second: what is the proper way of handling boolean values in JSON (how to convert JSON_TYPE.TRUE and JSON_TYPE.FALSE to bool)? Righ now I'm doing is something

Re: Space Cadet Keyboard

Wikipedia article and why default emacs key bindings are painful today. http://en.wikipedia.org/wiki/Space-cadet_keyboard http://ergoemacs.org/emacs/emacs_kb_shortcuts_pain.html

Re: C++/C mangleof inconsistency for OS X

Iain Buclaw via Digitalmars-d digitalmars-d@puremagic.com writes: (FYI - last time I checked GDC goes ahead and applied target-specific mangling on-top of pragma(mangle). So you can relax and assume nothing about the target). So does LDC. Actually, DMD does too on OS X, but only for

Re: C++/C mangleof inconsistency for OS X

Iain Buclaw via Digitalmars-d digitalmars-d@puremagic.com writes: Because of this, debugging in OSX is not as good as it could be (if you use DMD). All debuggers I've seen remove the leading '_' from symbols before they begin demangling symbols. And I noticed __cxa_demangle() is defined that

Space Cadet Keyboard (was Re: SDC needs you -- redux)

John Colvin john.loughran.col...@gmail.com writes: On Wednesday, 22 April 2015 at 16:27:59 UTC, Wyatt wrote: On Wednesday, 22 April 2015 at 15:44:03 UTC, Dan Olson wrote: Super and Hyper keys A veteran of the Lisp machines! I've been hoping for someone to manufacture a modern keyboard

Re: C++/C mangleof inconsistency for OS X

Michel Fortin michel.for...@michelf.ca writes: I think if you specify the mangling most of the time it's because you don't want the compiler to do it for you. But you should consider doing this: string mangleC(string name) { version (OSX) return _ ~ name; else return name; }

Re: SDC needs you -- redux

Atila Neves atila.ne...@gmail.com writes: Extra lisp libraries? How did you install it? I found my notes. I think it had to do with using flycheck, which I disabled. I am really ancient and set in my ways so distracted when code suggestions popup while I am typing. I just need to try again,

Re: extern(C++) linker errors

bitwise bitwise@gmail.com writes: I am trying to interface to C++, and getting linker errors. Below are my 3 source files and 2 build scripts with their associated errors. Can anyone see what I'm doing wrong? Hi, I think both examples need libstdc++ added when you link (-L-lstdc++). That

Re: C++/C mangleof inconsistency for OS X

Daniel Murphy yebbliesnos...@gmail.com writes: Jacob Carlborg wrote in message news:mh7mka$19r9$1...@digitalmars.com... And what about pragma(mangle), should that output the symbol name completely untouched? Yes. Then for systems that add underscore prefix to compiler identifiers, dmd

Re: SDC needs you -- redux

Brian Schott briancsch...@gmail.com writes: On Tuesday, 21 April 2015 at 15:01:59 UTC, Dan Olson wrote: Brian Schott briancsch...@gmail.com writes: For what it's worth, D-Scanner can output ctags information for D files. Brian, how about etags for emacs? Because the documentation for

Re: SDC needs you -- redux

Atila Neves atila.ne...@gmail.com writes: Better: https://github.com/atilaneves/ac-dcd Atila Yes, I grabbed that last fall. It's in my .emacs but disabled. I'll have to go back a try it again. It looked really good but I was having some sort of problem, I don't remember what. Probably

Re: C++/C mangleof inconsistency for OS X

Jacob Carlborg d...@me.com writes: On 2015-04-20 18:33, Dan Olson wrote: An observation on OSX w/ 2.067: mangleof for C++ (and D) names produces the actual object file symbol while mangleof for C names strips a leading underscore. Is this intended? If so what is rationale? I don't think

Re: SDC needs you -- redux

Brian Schott briancsch...@gmail.com writes: For what it's worth, D-Scanner can output ctags information for D files. Brian, how about etags for emacs?

Re: C++/C mangleof inconsistency for OS X

Dan Olson zans.is.for.c...@yahoo.com writes: Jacob Carlborg d...@me.com writes: On 2015-04-20 18:33, Dan Olson wrote: An observation on OSX w/ 2.067: mangleof for C++ (and D) names produces the actual object file symbol while mangleof for C names strips a leading underscore. Is this

Re: druntime unit test failures on FreeBSD

On Sunday, 19 April 2015 at 07:36:13 UTC, Jonathan M Davis wrote: I am consistently seeing this when I try and run druntime's unit tests on FreeBSD for either 2.067 or master: 0.000s PASS release64 object 0.000s PASS release64 core.atomic 0.008s PASS release64 core.bitop 0.000s PASS release64

C++/C mangleof inconsistency for OS X

An observation on OSX w/ 2.067: mangleof for C++ (and D) names produces the actual object file symbol while mangleof for C names strips a leading underscore. Is this intended? If so what is rationale? Demo $ cat showmangle.d XYZZY void dfun(int); extern(C++) void cxxfun(int); extern (C) void

Any D plugins for recent Xcode?

Just checking to see if anybody has D and Xcode playing together nicely. This may be the last hurdle to jump for enjoyable D use with iOS. I finally figured out a recipe to use symbolic debugging on armv7, but being able to click in source code to set breakpoints would be more fun that typing b

Re: Any D plugins for recent Xcode?

Jacob Carlborg d...@me.com writes: On 2015-04-18 19:30, Dan Olson wrote: Just checking to see if anybody has D and Xcode playing together nicely. Not for any recent version of Xcode. Michel Fortin wrote a puling for Xcode 3 [1], if you're interested. [1]

  1   2   >