April 11, 2008 [Issue 1985] import expression should return ubyte[] not string | ||||
---|---|---|---|---|
| ||||
Posted in reply to d-bugmail | http://d.puremagic.com/issues/show_bug.cgi?id=1985 ------- Comment #8 from wbaxter@gmail.com 2008-04-11 15:18 ------- (In reply to comment #7) > I think I understand your way of thinking. But the problem here is different. With void[] you can not do anything, so you have to cast. With ubyte[] you can use data as they are, because they have in fact specific type. Well, it's a specific type that represents raw memory. But I get your point too. If there were a void_without_pointers type that couldn't be used without casting, then I'd be happy for import("file") to use that. But with void[] getting scanned by the gc for pointers it's a no-go. If you do just one import("big_binary_file") it could add enough false pointers that your app would hold on to big gobs of memory it doesn't need to. -- |
May 27, 2012 [Issue 1985] import expression should return ubyte[] not string | ||||
---|---|---|---|---|
| ||||
Posted in reply to d-bugmail | http://d.puremagic.com/issues/show_bug.cgi?id=1985 dawg@dawgfoto.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dawg@dawgfoto.de Platform|x86 |All Version|1.028 |D1 & D2 OS/Version|Windows |All --- Comment #9 from dawg@dawgfoto.de 2012-05-27 03:16:35 PDT --- UTF validation and conversions can be done at compile time, although the interpreter is currently a little slow for this. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
Copyright © 1999-2021 by the D Language Foundation