To view parent comment, click here.
To read all comments associated with this story, please click here.
You do make a valid point. However, there was no physical way of doing it from what I could see. I cant remember how I did it at the time, but knowing me, I would have tried opening the file as a stream too and waiting for EOF, and that wouldn't have worked (or I wouldn't have posted this). And I tested it on C and perl, and other languages, and all provided a means of reading them.
So evidently, they weren't reading the files properly (or they were doing it in a really advanced way).
Either way, I got put off by only 1 response, that acknowledged why the problem existed, but didn't even attempt to rectify it and making the functionality possible. Its no good telling a developer you cant do it because its a 0 size, but not trying to fix the problem by working around it (or offering new functions). And I was in no way inclined to help a project, whose only compiler at the time was totally closed.
Its interesting to hear about more problems though you are having. I think that ultimately, by the time they get their act together, they will also have to compete against C++ 0x and new generations of C# and Java.
That is just my personal opinion though anyway






Member since:
2005-07-06
That's true for dmd which you have to download yourself but there's no licensing issue for gdc.
Well, these are not true filesystem, so I tend to agree that this is not really a bug that normal commands fails: after all a 'ls -l /proc/sys/kernel/osrelease' is lying to you by reporting a size 0, in fact it's silently failing..
But sure for a system programming language this is an issue, in my opinion the correct way to fix this is either to add an option to read so that it doesn't try to access the length of the file or to provide another function read_svfs (read special virtual fs) which does the same thing.
Well, new system, new issues, this is true whatever the system (I remember having a bug in Java's GC back in the data), I'm not sure you really tried very hard to have this issue fixed, did you enter a bug into bugzilla?
There are very real problems with D:
-the incompatible split Phobos/Tango (worked on but has been an issue for a long time)
-the not very efficient GC (I'm not sure that this is solvable: this is a price to pay for C compatibility..)
-the syntax: it's better than C++ or Java sure (not hard!), but when you compare it to Scala, it's not that good..