On Tuesday, 31 July 2012 at 13:16:57 UTC, akaz wrote:
I just discovered that. I find it surprisingly. Fear
surprisingly - surprising. sorry.
According to Wikipedia:
Phobos (Ancient Greek: Φόβος, pronounced [pʰóbos],
meaning fear or terror) is the personification of fear in
Greek mythology.
http://en.wikipedia.org/wiki/Phobos_(mythology)
I just discovered that. I find it surprisingly. Fear
Terror
On Tuesday, 31 July 2012 at 13:22:57 UTC, Tobias Brandt wrote:
On 31 July 2012 15:16, akaz a...@utopia.com wrote:
Phobos and Deimos are the two moons of Mars, which was the
original name of D.
That, on the other hand, was known to me. What I did not know,
was the fear factor... Maybe
On Tuesday, 31 July 2012 at 13:28:35 UTC, akaz wrote:
On Tuesday, 31 July 2012 at 13:22:57 UTC, Tobias Brandt wrote:
On 31 July 2012 15:16, akaz a...@utopia.com wrote:
Phobos and Deimos are the two moons of Mars, which was the
original name of D.
That, on the other hand, was known to me
On Tuesday, 31 July 2012 at 14:32:01 UTC, Dejan Lekic wrote:
That, on the other hand, was known to me. What I did not know,
was the fear factor... Maybe the library should have been
renamed to Deimos? :)
What do you think where the term PHOBia came from??
That, for one, I missed it! Thanks!
On Tuesday, 31 July 2012 at 14:32:01 UTC, Dejan Lekic wrote:
That, on the other hand, was known to me. What I did not know,
was the fear factor... Maybe the library should have been
renamed to Deimos? :)
What do you think where the term PHOBia came from??
And what about PHOBos? (PHOB
Hi,
In Linux kernel programming, there are some parts that are not
allowed to sleep (to be rescheduled). For example: interrupt
handlers, softirqs and tasklets.
Using functions that can sleep (for example: malloc, semaphores,
regular mutexes - unlike spin_locks, etc.) is forbidden inside
if needed, the operator !! (double exclamation mark) could be
defined.
it is just an idea, i do not have any specific use in mind.
i encountered the operator in RT operating systems book:
c!!e sends the message e along channel c
c?x assigns to variable x the value from c
maybe this could be
On Wednesday, 11 July 2012 at 14:08:55 UTC, deadalnix wrote:
On 11/07/2012 13:18, akaz wrote:
So why do you do a proposal if this is not needed ?
I did not ask for it, I only reminded that it is possible to
define it if needed. It's merely a suggestion. I was reading a
book and told myself
Well, then we're going to have to agree to disagree on that
one. While some
design decisions may have made more sense at the time they were
made or the
ultimate pros and cons may not have been clear at the time, I
think that zero-
terminated strings are one of the design decisions which was
Hi,
Reading about the C++11, I stumbled upon this:
http://www2.research.att.com/~bs/C++0xFAQ.html#gc-abi
Specifically (quote):
int* p = new int;
p+=10;
// ... collector may run here ...
p-=10;
*p = 10;// can we be sure that the int is still
If you are interested in D read this first:
http://dlang.org/garbage.html
You can find there e.g.:
Do not add or subtract an offset to a pointer such that the
result points outside of the bounds of the garbage collected
object originally allocated.
So `p+=10;` is already undefined behavior.
On Friday, 6 July 2012 at 15:39:40 UTC, Alex Rønne Petersen
wrote:
On 06-07-2012 16:07, Denis Shelomovskij wrote:
06.07.2012 17:43, akaz пишет:
Hi,
Reading about the C++11, I stumbled upon this:
I'll just add: Handling this case is basically impossible to do
sanely. You can't really know
On Friday, 6 July 2012 at 21:10:56 UTC, Simon wrote:
On 06/07/2012 16:39, Alex Rønne Petersen wrote:
On 06-07-2012 16:07, Denis Shelomovskij wrote:
06.07.2012 17:43, akaz пишет:
Never mind what D says, even in C/C++ just doing the p += 10 is
invalid.
Creating a pointer that points
Won't some functions doing just what addRange() and
removeRange() do solve that kind of problem (if necessary)?
That means, forbidding the GC to scan some memory area for some
time?
Like their C++11 counterparts:
void declare_reachable(void* p); // the region of memory
starting at p
On Tuesday, 3 July 2012 at 10:12:39 UTC, Iain Buclaw wrote:
Hi,
I'm going to be pushing gdc-4.8 package into debian this
weekend (give about a fortnight for it to land in sid) - is
Hi,
I understand there will be no gdc-4.7 package, so this won't be
available on Ubuntu 12.10 which
Bumping this as we still need to make a decision about this. As
recently as yesterday, someone on the GCC mailing list posted a
complaint about an optimization pass that assumed undefined
semantics for overflow. We need to have a stance about this,
since GDC is going into mainline GCC soon.
I agree that throwing an exception could be a good feature to
have, but it should *not* be the default. I want my systems
code to run at full speed when I know what I'm doing.
In the release version, yes. In the release version, array bound
checking is disabled, too.
But in the debug
What started out as C with classes started acquiring this
feature and
that feature until the whole thing is just a haphazard heap of
misfitting self-contradictory pieces, which requires an
enormous amount
of essentially-arbitrary rules just to clarify something as
simple as,
for example,
My latest issue with Java is the trend to add annotations
instead of keywords, like @Override, or the new type
annotations like @NotNull and so on.
Its slowly going to annotation hell.
It was never clear for me why use annotations instead of proper
keywords.
Yes, annotations are supposed to
It's hard to grep for (since with is
used in comments quite often),
Try to search for with( or with\s(, that are less common
in normal text.
There is no tool (maybe the compiler could provide such a tool)
to remove all comments?
That way, you could do:
cat file.d | tool | grep
Sorry for my 2nd intervention on this thread. I recently ported
some (not much) code from C to D. My impression was that D(2)
tries to be too many things at once. I even considered porting to
D(1) instead of D(2). What attracted me into the first place to D
was it promise to be a better C (and
On Saturday, 28 April 2012 at 19:58:03 UTC, foobar wrote:
* di files - a library should encapsulate all the info required
to use it. Java Jars, .Net assemblies and even old school;
Pascal
units all solved this long ago.
I strongly support this.
These are the flags used by DMD. If you can point Mono-D to
gdmd instead of gdc it might work. gdmd is a wrapper around
gdc that convert dmd flags to gdc flags.
I cannot. GDMD toolchain is not even present among those in
Mono-D.
OTOH, I still do not know how to pass -lortp regular flag to
I need some help with Mono-D.
I am on Linux 64 and I try to use both DMD 2.958 and GDC-4.6.3
However, I find difficult to:
-set the Toolchain per project; apparently, only global option
(Edit-Preferences-Other-D-Compiler Toolchains) exists
-add libraries per project; again, only global
I am a bit lost between pointers
(s-x or (*s).x) and values (s.x). For structures there are
pointers,
for classes there are no pointers?
Yes.
Ali
And migrating from std.stream.File (which was a class) to
std.stdio.File (which is a structure) lost me completely.
Why, in fact,
I should also add that I allocated my structure with:
(init)
s.filedesc = cast(File*)GC.calloc(1,File.sizeof);
(open)
(*(s.filedesc)).open(*(cast(string*)arg),w+b);
OMG! That solution works! Except that I was making a silly
mistake and thought that GC.alloc() prototype is similar to C's
(The data inside is not really what it should be, but that, at
least, is a debugging problem, not a segfault one).
Just to let you know that I did it. I was writing the good data
(as double), but it was my verification test that assumed it to
be int...
Now I corrected it and it works!
Any
Hi all,
I am trying to port some application based on a library called
mediastreamer2, part of linphone software.
The basic software component built on top of mediastreamer2 is
called a filter.
Basically, it is a C structure with parameters and some methods
(pointers to functions).
I should at that the __gshared attribute was added in distress,
but changed nothing. With or without it, the program still
crashes.
Thank you. But why do I lose access to my std.stream.File file?
Somehow, the variable gets unallocated, thus the file is closed
back?
With pointers of C it used to be so simple... variable remained
allocated untel the corresponding free().
I do not quite grasp this (a bit) awkward mix
std.file is more about files and directories, not file
contents. I've abandoned std.stream.File some time ago. I just
use std.stdio.File partly because stdio, stdout, and stderr are
of that type anyway. It works with ranges as well.
should be re-named std.folder, then, or std.filesystem.
OK, I converted into using the std.stdio.File. Without success,
the programs till crashes.
However, in the meantime:
A) why there is no parameter-less constructor for std.stdio.File?
I would like to have into my init function: s.filedesc=new
File() and, then, in my setter open method
33 matches
Mail list logo
