Steve,
Ah, yes, I totally forgot that prepared statements used a better format.
-[Unknown]
On 11/29/2011 9:42 AM, Steve Teale wrote:
On Tue, 29 Nov 2011 09:01:29 -0800, Unknown W. Brackets wrote:
Steve,
The type conversion you talk about (bigint -> double) probably happens
on 32-
Steve,
The type conversion you talk about (bigint -> double) probably happens
on 32-bit systems, no? Some of these things will definitely vary
depending on the database system.
I disagree with him on validation (although he's right about
constraints, speaking of atomicy), as others, but I t
Given the variety and fragmentation of clients, styles (above and
below), etc. never hurts to say that the message is interpolated.
-[Unknown]
On 11/29/2011 2:55 AM, Vladimir Panteleev wrote:
I wouldn't call making custom skins "trivial"...
Well, I'd expect one to be made to integrate the l
Comments interpolated below.
-[Unknown]
On 11/29/2011 1:29 AM, Vladimir Panteleev wrote:
What I'm concerned about, is that based on your recommendation of
vBulletin's threaded UI, you may have simply experienced poor UI?
For example, vBulletin only dedicates a measly amount of screen space to
#x27;re usually right
to do so.
Well, I guess more people are using Disqus and Facebook these days too.
-[Unknown]
On 11/29/2011 12:41 AM, Vladimir Panteleev wrote:
On Tue, 29 Nov 2011 10:39:35 +0200, Unknown W. Brackets
wrote:
Well, when I think "web forum software" I think ins
-[Unknown]
On 11/29/2011 12:20 AM, Walter Bright wrote:
On 11/28/2011 11:08 PM, Unknown W. Brackets wrote:
In contrast, I haven't a clue how to use NNTP on my iPhone. Go figure.
There is an NNTP newsreader app on the iphone, but the reviews on it say
it sucks. I haven't tried it.
Wi
Please see comments interpolated below.
-[Unknown]
On 11/28/2011 11:50 PM, Vladimir Panteleev wrote:
1. Well, I get threads, I really do. I understand their usefulness,
and how sometimes it's beneficial to completely ignore a branch - for
example, someone reporting an issue with a release on F
ot has a concept of "read", but then, I don't
frequent it (or Reddit or Digg) much.
-[Unknown]
On 11/29/2011 12:17 AM, Walter Bright wrote:
On 11/28/2011 11:06 PM, Unknown W. Brackets wrote:
3. Ignoring the comments about email replies (since they are easy
fodder), and
returni
That's just designers who don't get it. They're starting to nowadays.
I remember the WAP, I-mode, and etc. interfaces in SMF worked just fine
on small screens. Nowadays there are specialized iPhone interfaces.
And of course skins that scale fine.
In contrast, I haven't a clue how to use NNT
Walter,
Well, having authored web forum software, I suppose I'll make a few
remarks here. I seem to have gotten hit by a stray "forum software
writers (that's me) just don't get it."
1. Well, I get threads, I really do. I understand their usefulness, and
how sometimes it's beneficial to co
I have not read this entire topic, but what about the following:
case 5, .., 9:
Or even:
case 5.., 9:
This actually can be very logical, IMHO, because it's saying that 9 is
included very specifically.
Other possibilities that could be explored:
case for 5, 9:
case somekindofrange!(5, 9):
Well, I think it's more simple than that. Suppose I have a problem.
In Python, JavaScript, PHP, or some other similar language, I can solve
the problem in 1,000 lines of code.
In C++, etc. I can solve the problem in 5,000 lines of code.
Which is likely to have the most bugs? 1,000 lines or
Because you've never tried to use data initialized circularly. I wonder
what would happen in Java if you did?
-[Unknown]
Frank Benoit wrote:
Unknown W. Brackets schrieb:
Probably a silly idea, but what about (or similar):
static this: mod.name, mod.name2, mod.name3
{
}
For a depen
Actually, I didn't put that much thought into it. I see what you're
saying. If you leave them off, it has to behave as now (otherwise it
would break backwards compatibility.)
-[Unknown]
grauzone wrote:
static this as OP said not so good. Why would you need to specify no
dependencies? The wa
Probably a silly idea, but what about (or similar):
static this: mod.name, mod.name2, mod.name3
{
}
For a dependency list. I may be wrong, but afaik the main problems stem
from either wrong order or co-dependence (which needs to be solved by
the programmer.)
At least with this, you could as
Theoretically, you could recompile the GC to write to a log file any
time it frees anything.
For data processing, though, you really want to try to have a fixed
memory buffer. You've got to be hurting from the allocations and frees,
which if at all possible you should get rid of.
Also, if y
On Mon, 04 May 2009 14:53:41 -0400, Unknown W. Brackets
wrote:
I've always though of arrays and associative arrays as structs (which
really is what they are.) Thinking that way, this behavior makes
exact sense - down to .length being unchangeable and associative
arrays being unchang
uch arrays and
associative arrays. But that seems wrong to me too, and wouldn't come
free (speaking of efficiency) either.
-[Unknown]
Steven Schveighoffer wrote:
On Sun, 03 May 2009 05:25:09 -0400, Unknown W. Brackets
wrote:
This code works fine (D 2.x only):
class Test
{
;t make sense and could cause me serious problems. The
connection class can manage what parts of it you can modify or not, so
as long as I force you to use the one I already have, I'm safe.
-[Unknown]
Tyro[a.c.edwards] wrote:
On 5/3/2009 8:17 PM, Unknown W. Brackets wrote:
Well, if you re
r variable), should it be necessary to have a
setter to change the Socket? Can't the Socket handle its own
private/public-ness?
Arrays and associative arrays are the same, except that the members you
use are public.
-[Unknown]
Tyro[a.c.edwards] wrote:
On 5/3/2009 6:25 PM, Unknown W. Bracket
This code works fine (D 2.x only):
class Test
{
private int[int] _testMap;
public ref int[int] testMap() {return _testMap;}
}
void main()
{
Test test = new Test();
test.testMap[0] = 1;
}
Note the "ref". Otherwise, a value is returned which is not modifiable.
This will also fix test.a
tly into not making the same set of mistakes again.
Not that D isn't the better language, but there's so many variables in
situations like this that you really can't draw significant conclusions from
them.
All that said.. yay for going with D and having success with it, for whatever
For another real world example, we had a server daemon written in Java
and it took forever, had huge problems, cost us quite a bit, etc. etc.
We decided to have the same server rewritten in D, and it took
significantly less time, works correctly according to spec, doesn't
crash/hang half as of
So, really, all you want is a Visual Studio Language Service.
Jump to definition and syntax highlighting are relatively easy.
Refactoring is a bit more complex, and autocomplete is probably the most
complicated (to get right.)
It's really not impossible to write your own language service, and
from
that - once someone realizes that it can take less time throughout, it's
not hard to invest some upfront time. Especially during slow seasons.
It just has to get over the toppling point.
-[Unknown]
Walter Bright wrote:
Unknown W. Brackets wrote:
I know other managers at my company ha
I'm lucky, I'm a technical lead/manager at work, so I get to say "for
this project, we're using D." And then it happens. Muhahaha. We're a
small shop but I enjoy my small amount of power.
Soon it will happen, just have to lay in the ground work. I know other
managers at my company have no
Specifically, I'm concerned about ".<>". What is that? I guess it's a
namespace, and so it's an empty one. That just seems wrong... like D
having "x..y" or "x.!()y", which it definitely doesn't have.
-[Unknown]
Christopher Wright wro
in performance critical code.
-[Unknown]
Benji Smith wrote:
Unknown W. Brackets wrote:
I wonder what the overhead times were. He should've timed them both
and listed them separately. For example, is DynamicMethod a complete
win, or is the dynamic keyword cheaper as far as base
I read until I hit this:
4. if (o__SiteContainer0.<>p__Site1 == null)
And I was suddenly hit with a huge feeling of "I'm glad D doesn't look
like this." Seriously, I hope this is some sort of decompiled syntax
and not actually valid.
I wonder what the overhead times were. He should'
It really is /etc not /usr/etc. I said the sudo thing just in case you
hadn't verified it exists in /etc.
The following locations are checked on Mac OS X:
The current directory (`pwd`)
The home directory ($HOME)
The directory of argv0 (e.g. /usr/local/bin)
/etc/
It will not look in /usr/etc e
Well iirc, you need to:
sudo cp dmd.conf /etc/dmd.conf
Which will (potentially) require editing of dmd.conf for the correct
paths. I usually put phobos's src in /usr/src/phobos or .../d/phobos,
but I can't remember if it was different on Mac... (some things have
/private before them there...
So, how often do you have an int array that you do not intend to append
elements to, but yet intend to change the values within it? Excluding
preallocation, of course.
Every time I use an int[], or honestly practically any array, I'm either
creating it or reading it. Nonetheless, I don't do
(and I know I said "char[] should _be_ a StringBuilder", which probably
caused the confusion - sorry. I was trying to differentiate the two, I
worded it poorly for what I actually meant.)
-[Unknown]
Unknown W. Brackets wrote:
1. Well, I think that immutable(T[]) ~ immutable(T[])
Robert Jacques wrote:
On Sat, 25 Apr 2009 20:17:00 -0400, Unknown W. Brackets
wrote:
Let me say it a different way:
split() returns results that are, often, stored or compared. It is
not often that these results are concatenated to or modified.
Possibly, they may not be sliced (further
o avoid this however,
because changes in the language, means changing the lexer obviously.
An viable alternative would be to use some scanner generator, that suits
my needs. Now only the grammar needs to be updated.
The DCoder thing sounds interesting.
/ab
Unknown W. Brackets skrev:
I went an
e the solution
of using a "String" class. D, in my opinion, proved the latter was not
necessary; I hold that the former isn't either.
-[Unknown]
Robert Jacques wrote:
On Sat, 25 Apr 2009 14:21:49 -0400, Unknown W. Brackets
wrote:
I'm not talking about invariant(char)[], I
copy.
-[Unknown]
Robert Jacques wrote:
On Sat, 25 Apr 2009 13:30:22 -0400, Unknown W. Brackets
wrote:
What about simply using the const/invariant information?
After all, an "array builder" is a mutable array. If you don't want
to extend it, it should be invariant or const -
What about simply using the const/invariant information?
After all, an "array builder" is a mutable array. If you don't want to
extend it, it should be invariant or const - e.g. invariant(string).
I've always thought the separation of strings and string builders,
arrays and array builders, e
The only downside to this is, it's a Bad Thing to have the size of an
array be different between GC's, but I think it's probably not entirely
avoidable.
But, I really think it's the only good way to do it, imho. Maybe the
exact implementation is different, but creating a new type just seems
Well, a range of an associative array is a possibility (not a slice, but
e.g. from std.algorithm.)
I think it'd be a mistake to discount that. Being able to treat
associative arrays like arrays, in some cases (e.g. with count(), etc.)
is nice. That said, i don't even know that std.algorithm
Well, if they're in the same section, the compiler _could_ detect this
itself, couldn't it? I mean, it already does an optimization pass
before the codegen, it could theoretically do another collapse pass
after that.
I don't know how easy that would be, or if it would be worth it, but it
wou
I went and rewrote the bulk of the main parser/lexer in a way that was
more VSIP-friendly, which worked out for me. Unfortunately, it's just a
separate thing, and I need to update it badly at this point.
One problem is, you really want to be able to scan/lex by line. If you
don't do some cac
.
-[Unknown]
Leandro Lucarella wrote:
Unknown W. Brackets, el 18 de abril a las 16:51 me escribiste:
Well, I guess it would be doable to guarantee destruction, but *only* if
order of destruction was not guaranteed.
Yes, of course, order *can't* be guaranteed (unless you add read/write
bar
e would be unacceptable.
I may be wrong, but I'm pretty sure std.stream's files do not work as
you suggest. BufferedFile may, but I do not think File does (aside from
OS buffers and journals which are fine; an fsync is not mandatory.)
-[Unknown]
Leandro Lucarella wrote:
Unknown W. Bracke
The simple solution is this:
1. If your class object only involves memory, freed OS handles, etc., it
should be used as-is. This is most class objects. Destructors are
needed to clamp resource use (see File class.)
2. If your class object involves hardware handles, transactional
assurance,
Does waiting for a keypress in the client thread do you any favors?
Also, you can get some mileage by doing a select() (see SocketSet) on
the socket first. This will tell you if you need to accept(), and also
allow you to do timeouts. I'm a big fan of non-blocking sockets, you
can improve co
uot;, I'll still call it "an
API that uses a temporary file."
-[Unknown]
Kagamin wrote:
Unknown W. Brackets Wrote:
Well, I'm not so sure. Every time you invent meta data, someone will
invent a language that goes outside that meta data. It's reality.
API will do the
about personal, mostly irrelevant, opinions. Again, you need to contact
and discuss this issue with a lawyer who has passed through your
region's licensing requirements to be able to properly (and legally)
advise you on this matter.
-[Unknown]
Chris wrote:
"Unknown W. Brackets"
That is a very common clause. The idea, as far as I understand, is that
if the compiler were to break - and your client were to sue you because
of this - you can't sue down the chain.
From the same directory, readme.txt:
"The optimizer and code generator sources are
covered under a separate l
as far as reflection, D already embeds TypeInfo and such. A
lot of reflection is already possible - a library just needs to be
written that does it.
-[Unknown]
Kagamin wrote:
Unknown W. Brackets Wrote:
a standard way to integrate a compiler into an IDE
You meant *compilers*? D1, D2, D3 etc
, and it's a very logical part of the build process.
-[Unknown]
Walter Bright wrote:
Unknown W. Brackets wrote:
Of course, I'm sure a better API could be devised. This sort of
format, if properly standardized, could be used to make IDEs much more
efficient. It would also allow for m
Actually, I think it would be much more fruitful to have a standard way
to integrate a compiler into an IDE. An API would be needed with things
like: (all optional)
1. Lex a file (returning basic token information.)
2. Parse a file (returning some sort of standardized syntax tree.)
3. Compile
D is better as a language, imho. You never know when Apple will scrap
Mac OS X and do a new operating system. Who knows, maybe iPhone OS 5.0
will be written in D? It's extremely improbable, but it's not impossible.
Allocators have many uses. When integrating (as with a plugin) into
other s
No, I agree. I think for the sake of templating, improving the error
message is the best option - probably #3 (special case error message) imho.
-[Unknown]
Andrei Alexandrescu wrote:
Steve Teale wrote:
Unknown W. Brackets Wrote:
Steve,
It's not exactly prose, but the error messa
Steve,
It's not exactly prose, but the error message is correct. It says:
"Error: new can only create structs, dynamic arrays or class objects,
not char[]'s."
So:
1. You didn't try to allocate space for a struct (e.g. new struct_t.)
2. You didn't try to allocate space for a dynamic array (n
Yes, well, the question was about new not about arrays...
-[Unknown]
Steven Schveighoffer wrote:
On Sun, 22 Mar 2009 18:43:58 -0400, Unknown W. Brackets
wrote:
The new construct allocates memory. You can "new" anything that
requires a set amount of memory.
This is equivale
Actually, dmd is so fast I never bother with these "build" utilities. I
just send it all the files and have it rebuild everytime, deleting all
the o files afterward.
This is very fast, even for larger projects. It appears (to me) the
static cost of calling dmd is much greater than the dynami
The new construct allocates memory. You can "new" anything that
requires a set amount of memory.
This is equivalent to what you want:
auto s = new char[0];
Which creates a new dynamic array with no length (yet.) You can resize
it later. Remember, that is not the same as saying:
char[0] s
58 matches
Mail list logo
