Hi,
> >
> > All files in that folder are dated July 2009. Is there some newer
> > script you were referring to?
> >
>
> Wish I am able to send you more recent code :(
>
check the Phoenix project in wxWidgets SVN. It doesn't generate SWIG though, it
generates SIP. But the infrastructure could b
> For once, I agree with Bearophile. The adjacent string concatenation was a
> very
> very early feature, and the ~ completely supplants it. While I don't think it
> causes many problems, it's a pointless redundancy and should be removed.
Agreed; it seems to be a minor change, and the issue of
I found a confusing part :
Here is an abbreviated declaration for NSString:
extern (Objective-C) class NSComboBox ...
This declaration [...] will let know to the compiler that the NSColor class
exists
=P
Otherwise seems nice but I'll let people that know DMD answer
--Auria
> I posted on my blo
IMO this could be added, with the documentation specifying the implementation
doesn't need to best fast. So people who want quick development for things that
don't need high performance may use it, while people coding for performance
just need not use it. The compiler may try to optimize it if i
Hi,
>
> The C syntax is unspeakably ridiculous, useless, and downright
> dangerous. It shouldn't compile.
>
> In the past, Walter has mentioned a weak argument for retaining C-style
> array declaration syntax, although I personally find it very
> unconvincing. But C's hideous function pointer
> I receive a statement every six months from the publisher, and the next
> one should come, I think, around October. Until then, one indicator is
> the Amazon sales rank, which right now is around 150K (lower is better;
> this is not a great rank). A large jump in adoption hasn't happened at
Very right, and even more I might add a thing : the STL itself is just HUGE;
and unless you live in a shell, you're going to use some library; that some
library in all likeliness will include the STL directly or indirectly; and each
and everyone of your files end up building the entire STL every
Agreed, and if static verification is ever implemented (like there isn't
already enough to do on D ;) I can very well imagine adding contract blocks
with the "pure" keyword (or is it an annotation now?)
> On Saturday 31 July 2010 18:33:09 bearophile wrote:
> > D contract programming lacks the 'o
Pragmatically, I seem to have noted that in languages with low level strings,
people invariably come up with librairies that provide higher-level strings.
C/C++ provided low-level strings only initially, then a not-so-powerful
std::string; and we saw QString, wxString, irr::string, BetterString,
Rainer Deyke Wrote:
> On 5/30/2010 15:53, Philippe Sigaud wrote:
> > There are some simple containers I'd like to see in std.containers:
> >
> > - a priority queue
> > - a heap
> > - a stack, a queue
> > - a set
>
> Any container that supports pushing and popping on one end can be used
> as a st
> I think Walter said this can't be implemented :)
> The items alignment of function arguments used by D tuples is not fitting to
> return a struct. I have not understood the details of this thing, and in the
> end I don't care if returning a struct can decrease performance a bit...
>
well, it
If there's one thing I need to agree with there, it's definitely having more
than one return value.
C/C++ have it really awful by passing pointers, and then you need to document
it's an "out parameter" (I know this has become very common to most of us, me
included, but when I first saw this - y
In my experience (not related to DCollections), having interfaces is useful to
ensure reduced coupling, thus enabling the use of mock classes for unit tests
(or simply to test your module, when your module needs to use services provided
by another module that is being written by a colleague but
> The example is outdated. Now it's like
>
> connect(m_historyHome, "triggered", this, "slotHome").
>
Interesting. Does QtD use some MOC-like to generate code like C++ Qt, or is
there some magic?
I was searching for examples of how it was done, but if they're outdated... ^^
Hi Justin,
looking at QtD, it seems like it can be done :
In file
http://www.dsource.org/projects/qtd/browser/demos/browser/browsermainwindow.d
m_historyHome.triggered().connect(&this.slotHome);
// ...
public:
void slotHome()
{
> 6. propagate error productions
>
> [...]
>
> This can be done in a compiler by replacing every production that produces an
> error with an error production (i.e. a NaN) and then propagate them. For
> example, for the expression:
>
> z = x + y;
>
> if y is undefined, print the error message
Nick Sabalausky Wrote:
> I'm bringing this over here from a couple separate threads over on "D.learn"
> (My "D1: Overloading across modules" and bearophile's "Enum equality test").
>
> Background summary:
>
> bearophile:
> > I'm looking for D2 rough edges. I've found that this D2 code
> > compi
Don Wrote:
> This issue is inspired by bug 3918.
>
> float f;
> if (f) ...
>
> This currently compiles, but if the condition is true, what can you
> conclude about f?
> Obviously it's not zero, but can it be NaN?
> If it's just translated to: if (f!=0) ..., then f could be NaN.
> Likewise, if
Walter Bright Wrote:
> Jacob Carlborg wrote:
> > Why would you remove such a useful feature if it's already implemented?
> > I think too often people just complain when they don't like something
> > and when they do like something they just sit silently. Perhaps they use
> > IDEs when compiling
Andrei Alexandrescu Wrote:
>
> Disallowing hiding vertically in nested scopes has been quite
> successful. Also, D's no-hijack stance is also shaping up to be a hit. I
> am therefore thinking - why not apply the no-hijack rule throughout the
> language?
>
> If one symbol leads to working code
> So I was thinking of this:
>
> class LotterySimulation : Lottery, Figure {
> override(Lottery) void draw();
> override(Figure) void draw();
> }
>
> This is easy to implement, scales well, and has good real world uses.
> What say you?
>
One vote in favor :)
I'm admittedly not a D expert, and have not written compilers; but the first
thing that came to my mind is that the second fun() you posted was not an
override, but overload. i.e. the same as the following, except with inheritance
:
print(int a) { /* ... */ }
print(float a) { /* ... */ }
print(
OS X uses \n. \r dates from OS 9 (see http://en.wikipedia.org/wiki/Newline)
As simple as that ;)
> For our resident Mac users:
>
> I know (or at least have heard) that Mac's EOLs are traditionally '\r'. But,
> mac directory separators are traditionally ':' and I know that these days
> macs can
Paul D. Anderson Wrote:
> I was browsing the Python spec yesterday and came across this interesting and
> useful syntax:
>
> "/" (one slash) means floating point division, e.g. 5/2 = 2.5 even though 5
> and 2 are integers
>
> "//" (two slashes) means integer (floor) division, e.g. 5.0//2.0 = 2
Ah, and also :
Andrei Alexandrescu Wrote:
> Marianne Gagnon wrote:
> > Like someone else pointed out, existing keywords could be reused :
> >
> > bool empty
> > {
> > in(bool value)
> > {
> > _my_empty = value;
> > }
Andrei Alexandrescu Wrote:
> Marianne Gagnon wrote:
> > Or, alternatively, if you really wish to keep them separate, bool empty= {
> > ... } isn't intuitive, as Andrei pointed out, but is already less
> > error-prone than the empty-body declaration idea I believe
>
>
> The alternative is to have a unique syntax for properties. Ideally, the
> syntax should be intuitive and mimic its use. After much fiddling, and
> based on n.g. suggestions, Andrei and I penciled in:
>
>bool empty { ... }
>void empty=(bool b) { ... }
>
> The only problem is when a
Jarrett Billingsley Wrote:
> On Sat, Aug 1, 2009 at 10:14 AM, Michel Fortin
> wrote:
>
> > The best simple solution to that property problem I've seen up to now is to
> > define "getProperty" and "setProperty" and have the compiler automatically
> > check for these functions when it encounters t
>
> I think the poll might have been skewed due to context (forget my
> newsgroup poll, that was worthy of an abortion, but I also didn't mean to
> submit it :), I'm talking about Ary's)
>
> The question was asked, what do you think this code means. In the context
> of D, where you know a
In C++, I use comments for 2 purposes :
1) Add documentation
2) Disable code (also with #if 0 ... #endif)
Since those two actions are logically very different, I believe it's nice that
they're separate.
Why I *would* propose, however, is to get rid of /** ... */, and say that /*
... */ is alw
> >> LDC packages are available for 0.9, but it has some bugs still...
> >
> > Personally I can't wait to try LDC!
>
> It's available as a tarball, "ldc-0.9-mac.tar.bz2", including Tango.
Where is this file available? I've been browsing the LDC website without
finding anything beyond the sou
mac osx 32 bit intel
mac osx 64 bit intel
linux 64 bit
windows 64 bit
32 matches
Mail list logo
