== Quote from KennyTM~ (kenn...@gmail.com)'s article
> It's very *unportable* to write a string in your way.
Yes, that's probably true.
> If D allowed non-UTF encoding without error, it's possible that a string
> in those settings got misinterpreted, but it's not easy to determine when.
Could be
== Quote from KennyTM~ (kenn...@gmail.com)'s article
> You could use x"" string, or just escape those characters
> auto x = x"f1f2f3 f4";
> auto y = "\xf1\xf2\xf3\xf4";
> (And if your "string" is not a UTF-8 string at all, you should use a
> ubyte[], not char[].
> const(ubyte)[] z =
== Quote from Daniel Gibson (metalcae...@gmail.com)'s article
> Once a feature is deprecated, the compiler will treat using it as an
> error - *if* you don't use the "-d" switch ("Allow deprecated features").
> I think this should be acceptable for you?
> Cheers,
> - Daniel
Seems good. Sorry, I di
> This has been acknowledged. Yes, removing delete in D2 will break
> compatibility with existing code. However, I'm sure that at an early
> stage, the compiler will probably issue error messages once it
> encounters delete statements, for which the fix is quite easy: just
> remove them, and recomp
== Quote from Denis Koroskin (2kor...@gmail.com)'s article
> You can use import("file.txt"); to import files (text or binary) at
> compile time.
Interesting - I didn't know this. It's true that most of strings will be
probably
loaded from some file in final application...
This post is in fact mainly about removing delete, but I didn't wont make
everyone angry just with title.:) I am sure not expert to language design, so
I should probably be quiet, but I have question.
My question is: Didn't break it (i.e. removing delete) compatibility?
In my opinion every decisio
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
> On 4/19/11 1:04 PM, Timon Gehr wrote:
> > Steven Schveighoffer wrote:
> >> And one other note -- delete will eventually be deprecated. In order to
> >> free memory, you must use clear and GC.free.
> >
> >> -Steve
> >
> >
== Quote from Steven Schveighoffer (schvei...@yahoo.com)'s article
> On Mon, 18 Apr 2011 04:31:26 -0400, %u wrote:
> > Is it necessary free memory allocated for member of structure, like in
> > C? I
> > suppose not (we have gc). Example:
> >
> > struct BITMAP {
> > (...)
> > ubyte[] pixels;
> > }
I see...thanks for answer. And if I call "delete bitmap", it will be removed
immediatelly, or it doesn't matter and gc will remove it when it will start its
cycle?
So even ubyte[] pixels will be allocated on the stack ?? What is prefered method
to allocate large byte array, then? Should I use mal
Hello, I have array of type vertex_t vertices[] where vertex_t is:
struct vertex_t {
float[3] xyz;
ubyte[4] color;
...
}
Now, I would like use instead of array "float[3] xyz" "vec3f xyz", where vec3f
is:
struct vec3f {
float x, y, z;
...some functions...
}
where I have defined some op
10 matches
Mail list logo
