Re: in dub single file build how to pass "-J" options?
stringImportPaths
Re: text based file formats
On 19/12/2022 4:56 AM, Robert Schadek wrote: > * xml, there is some code already, the old std.experimental.xml code I've toyed with std.experimental.xml. I'm not convinced that it is a good code base for inclusion. * no return by ref As a bit of a follow up of what we were talking about on BeerConf: Because these are not data structures, they won't own externally facing memory (thats the GC job). So these lifetimes issues with ref should never be encountered. > * make it @safe and pure if possible (and its likely possible) pure is always a worry for me, but yeah @safe and ideally nothrow (if they are forgiving which they absolutely should be, there is no reason to throw an exception until its time to inspect it).
Re: Beerconf for dconf online 2022
Hope everyone got your brews ready! I for one, have some nice cold iced water, in 29 degree temperatures you must stay hydrated! https://meet.jit.si/Dlang2022DConfOnline
Re: Beerconf for dconf online 2022
On 16/12/2022 1:53 AM, rikki cattermole wrote: Reminder this is happening tomorrow! In ~24 hours Will be posting in about an hour. Get your brews if you haven't already!
Re: DConf Online '22 this weekend! Videos are up!
Here is a mailto link that'll setup an email ready to go! mailto:q...@dlang.org?subject=PersonToAsk=Question%0D%0A%0D%0A--%20YourName%20anonymous%3F%0D%0A%0D%0AI%20want%20a%20prize!
Re: Beerconf for dconf online 2022
Reminder this is happening tomorrow! In ~24 hours
Re: How to compiler dlang code on Apple M1?
Which ldc did you install? Was it: ldc2-1.30.0-osx-arm64.tar.xz
Re: Idiomatic D using GC as a library writer
ALl it means is certain memory patterns (such as writes), will tell the GC about it. Its required for pretty much all advanced GC designs, as a result we are pretty much maxing out what we can do. Worth reading: https://www.amazon.com/Garbage-Collection-Handbook-Management-Algorithms/dp/1420082795
Re: Why can't D store all UTF-8 code units in char type? (not really understanding explanation)
On 03/12/2022 11:32 AM, Ali Çehreli wrote: On 12/2/22 13:44, rikki cattermole wrote: > Yeah you're right, its code unit not code point. This proves yet again how badly chosen those names are. I must look it up every time before using one or the other. So they are both "code"? One is a "unit" and the other is a "point"? Sheesh! Ali Yeah, and I even have a physical copy beside me! P.s. Oh btw Unicode 15 should be coming soon to Phobos :) Once that is in, expect Turkic support for case insensitive matching!
Re: Why can't D store all UTF-8 code units in char type? (not really understanding explanation)
On 03/12/2022 10:35 AM, Adam D Ruppe wrote: On Friday, 2 December 2022 at 21:26:40 UTC, rikki cattermole wrote: char is always UTF-8 codepoint and therefore exactly 1 byte. wchar is always UTF-16 codepoint and therefore exactly 2 bytes. dchar is always UTF-32 codepoint and therefore exactly 4 bytes; You mean "code unit". There's no such thing as a utf-8/16/32 codepoint. A codepoint is a more abstract concept that is encoded in one of the utf formats. Yeah you're right, its code unit not code point.
Re: Why can't D store all UTF-8 code units in char type? (not really understanding explanation)
char is always UTF-8 codepoint and therefore exactly 1 byte. wchar is always UTF-16 codepoint and therefore exactly 2 bytes. dchar is always UTF-32 codepoint and therefore exactly 4 bytes; 'Ğ' has the value U+011E which is a lot larger than what 1 byte can hold. You need 2 chars or 1 wchar/dchar. https://unicode-table.com/en/011E/
Re: How do you print all Unicode characters in a range - I want the subscripts, can't google a range of Unicode.
The output will be bad because of Windows specific behavior related to
not outputting as UTF-16.
This will print all the characters in the block "Superscripts and
Subscripts".
The Unicode database is very out of date (just waiting for merge for
update), but should be ok for this example.
```
import std.uni : unicode;
import std.stdio : writefln;
void main() {
foreach(c; unicode.InSuperscriptsandSubscripts.byCodepoint)
writefln!"U+%X = "(c, c);
}
```
Unfortunately I'm not seeing an obvious way of determining
subscript/superscript from what we have.
You can do it with the help of[0] via Super/Sub field values, which
originate from UnicodeData.txt's Decomposition_Type field, but you
shouldn't parse that if you only want just this one set of values.
[0]
https://www.unicode.org/Public/15.0.0/ucd/extracted/DerivedDecompositionType.txt
Re: Thinking about the difference between fixed and 'dynamic' arrays.
Okay you have misunderstand a lot here. We have two types of arrays: - Static, fixed sized stored on stack. - Dynamic, variable sized, stored on the heap. However dynamic arrays are not actually a distinct type in the type system, its a language extension to use runtime hooks using the GC. What dynamic arrays are in the language is just slices. A slice is a length + pointer pair. This is where almost all of the syntax for dynamic arrays come from. ```d int[] slice; ``` That is a slice. ```d slice ~= 32; ``` Now it is a dynamic array as it was allocated via the GC. ```d int[4] staticArray; slice = staticArray[]; ``` The slice is now able to modify the staticArray!
Re: Beerconf Noveber 2022 -- Turkey edition
https://meet.jit.si/Dlang2022NovemberBeerConf
Re: Beerconf Noveber 2022 -- Turkey edition
~T-3 hours Time to go acquire your favorite brews if you haven't already!
Re: D + Qt + QtDesigner
Don't forget about UI automation too! That's a key feature people always seem to forget... (unless you require it).
Re: Beerconf Noveber 2022 -- Turkey edition
On 18/11/2022 2:16 PM, Ethan Watson wrote: On Saturday, 12 November 2022 at 21:51:38 UTC, Steven Schveighoffer wrote: # BEERCONF! Reminding myself to remember this for a change. Don't worry, you won't miss it this time! I'll bug you everywhere I can when I (or someone else) put the link up ;)
Re: Is defining get/set methods for every field overkill?
I wouldn't bother. They are const, they can't change. Nothing to protect, nothing to synchronize.
Re: Release D 2.101.0
On 16/11/2022 2:13 PM, torhu wrote: On Tuesday, 15 November 2022 at 20:54:03 UTC, Iain Buclaw wrote: Glad to announce D 2.101.0, ♥ to the 63 contributors. For some reason my project build fails with this version, but only the x86 release build. Only tried it on Windows. This is the error, I'll post a bug report if I can narrow it down more: Error C:\prog\dmd\windows\bin\dmd.exe failed with exit code -1073741795. Yeah, you'll want to use dustmite. Hopefully the project isn't too big.
Re: Actual lifetime of static array slices?
On 15/11/2022 5:10 PM, Elfstone wrote: I just checked the DIP list and #1000 is marked superseded. Any idea what supersedes it? The implementation.
Re: Call for action: Easily improve D's ecosystem - DUB documentation improvements
I've filled in some details about shared libraries wrt. plugins the issue for it. Will need compiler specific information CC: Walter, Martin, Iain. Still massive shame that dmd is still a write off for Windows support when using D from D. Wahoo export + ModuleInfo + DLLs. Oh and don't forget about the no Unicode exported on Windows!
Re: Drawing a line code
On 07/11/2022 10:29 PM, Joel wrote: Ok, this is working: I'm glad to hear it! Pathing algorithms can be quite fun to mess around with.
Re: Drawing a line code
On 07/11/2022 5:48 AM, Joel wrote: The algorithm is too hard for me to work out and dg2d doesn't help either. I want my code fixed up so that works from any two points. Its not as complex as that page initially looks. ``` plotLine(x0, y0, x1, y1) dx = abs(x1 - x0) sx = x0 < x1 ? 1 : -1 dy = -abs(y1 - y0) sy = y0 < y1 ? 1 : -1 error = dx + dy while true plot(x0, y0) if x0 == x1 && y0 == y1 break e2 = 2 * error if e2 >= dy if x0 == x1 break error = error + dy x0 = x0 + sx end if if e2 <= dx if y0 == y1 break error = error + dx y0 = y0 + sy end if end while ``` That is the pseudo code you want. Its just a matter of typing the variables to something like int. I can recommend: https://www.amazon.com/Computer-Graphics-Principles-Practice-3rd/dp/0321399528 and https://www.amazon.com/Computer-Graphics-C-Version-2nd/dp/0135309247 (The updated version should be fine too) If you wish to understand it.
Re: Linking not working properly Windows 11
I've looked up three of those names, they are all deprecated. I'm wondering if Microsoft have removed them.
Re: Linking not working properly Windows 11
Try ldc, if that works then its just a missing library that needs to be linked against regarding MS CRT.
Re: Makefiles and dub
On 06/11/2022 1:16 AM, Imperatorn wrote: On Saturday, 5 November 2022 at 11:38:09 UTC, rikki cattermole wrote: We have a few build formats that dub can generate for you automatically: ``` visuald - VisualD project files sublimetext - SublimeText project file cmake - CMake build scripts build - Builds the package directly ``` Unfortunately none of them are make, it would be nice to have that if you are looking to contribute! Wait, dub can generate all those? I only knew about visuald build is just dub and doesn't emit any project files. But yes, it has two others (although idk how much they get used, or how complete).
Re: Makefiles and dub
We have a few build formats that dub can generate for you automatically: ``` visuald - VisualD project files sublimetext - SublimeText project file cmake - CMake build scripts build - Builds the package directly ``` Unfortunately none of them are make, it would be nice to have that if you are looking to contribute!
Re: Unit testing a function returning void
You could redirect stdout to a file of your choosing and test against that. Although ideally you would instead take as an argument to print some sort of output range or Appender. Then you could test against that instead.
Re: Make IN Dlang
Something to consider: dub can be used as a library. You can add your own logic in main to allow using your build specification to generate a dub file (either in memory or in file system).
Re: Beerconf October 2022
On 02/11/2022 4:05 AM, Mike Parker wrote: On Tuesday, 1 November 2022 at 11:54:45 UTC, data pulverizer wrote: It might just be my browser (Chrome) but I've noticed that there's nothing in the events calendar (https://dlang.org/calendar.html). Wouldn't it be helpful to include these sorts of things in the calendar so that people visiting the site would be aware of them? I don't think anyone involved in organizing BeerConf knew that was there. That's the first I've seen it. I've certainly seen it before, but its not like I have access to it (assuming it works).
Re: Beerconf October 2022
And now for some good news! Its almost Halloween, so grab your candy and any spooky brews you may have, and join us for a ghostly chat! https://meet.jit.si/Dlang2022OctoberBeerConf
Re: Replacing tango.text.Ascii.isearch
On 29/10/2022 11:05 AM, Siarhei Siamashka wrote: And as for the D language and Phobos, should "ß" still uppercase to "SS"? Or can we change it to uppercase "ẞ" and remove German from the list of tricky languages at https://dlang.org/library/std/uni/to_upper.html ? Should Turkish be listed there? That particular function, is based upon the simple mappings provided by UnicodeData.txt and (should be) in compliance of the Unicode standard. The only thing we need to do is regenerate the tables backing it whenever Unicode updates. Note the behavior you are asking for is defined in the Unicode database file SpecialCasing.txt which have not been implemented. ``` # The German es-zed is special--the normal mapping is to SS. # Note: the titlecase should never occur in practice. It is equal to titlecase(uppercase()) 00DF; 00DF; 0053 0073; 0053 0053; # LATIN SMALL LETTER SHARP S ``` That file is how you support languages like Turkish. We currently don't have it implemented. It requires operating on a whole string and to pass in what language rules to apply (i.e. Turkish, Azeri).
Re: Importing modules under DUB on Windows
On 29/10/2022 4:15 AM, DLearner wrote: However, going forward, I don't want copies of OM anywhere other than UD. If you want your own private library on your system (that will get used a lot), you can create a package and use ``$ dub add-local .`` to add it to the available packages for lookup, without needing a version control system. Then you just add it as a dependency on an as needed basis (use ``*`` for version should work fine).
Re: Importing modules under DUB on Windows
On 28/10/2022 5:40 AM, DLearner wrote: Maybe fewer people use it under Windows, so Windows constructs don't get exercised so much. I have actively contributed to dub specifically for Windows in the last year :) There is enough of us. Also UNC paths (those with drives and then the slash) are actually absolute, not relative. There are relative ones, but the path processing in dub is pretty simplified. You have to stick to completely relative, POSIX style. https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats You should be working with relatives paths in respect to the $PACKAGE_DIR, not the compiler or any root location of your file system (such as the drive would indicate). https://dub.pm/package-format-json.html#environment-variables
Re: Replacing tango.text.Ascii.isearch
On 26/10/2022 6:49 PM, Siarhei Siamashka wrote: On Wednesday, 26 October 2022 at 05:17:06 UTC, rikki cattermole wrote: if you are able to ignore that Unicode is a thing, I'd recommend it. It is complicated, as we humans are very complicated ;) I can't ignore Unicode, because I frequently have to deal with Cyrillic alphabet ;) Also Unicode is significantly simpler than a set of various incompatible 8-bit encodings (such as [CP1251](https://en.wikipedia.org/wiki/Windows-1251) vs. variants of [KOI-8](https://en.wikipedia.org/wiki/KOI-8) vs. [ISO/IEC 8859-5](https://en.wikipedia.org/wiki/ISO/IEC_8859-5)) that were simultaneously in use earlier and caused a lot of pain. But I'm surely able to ignore the peculiarities of modern Turkish Unicode and wait for the other people to come up with a solution for D language if they really care. Cyrillic isn't an issue. Lithuanian, Turkish and Azeri are the ones with the biggest issues. There is a bunch of non-simple mappings for Latin, Armenian and Greek, but they are not language dependent. There is six conditional ones which are all Greek. So if you are not dealing with these languages (even if you are, a simple replace should be easy to do for most), you should be fine with the simple mappings supported by std.uni.
Re: Replacing tango.text.Ascii.isearch
On 26/10/2022 6:06 PM, Siarhei Siamashka wrote: Should we ignore the `"D should strive to be correct, rather than fast"` comment from bauss for now? Or some actions can be taken to improve the current situation? Bauss is correct. It should be implemented but it does not need to be fast. But yeah, if you are able to ignore that Unicode is a thing, I'd recommend it. It is complicated, as we humans are very complicated ;)
Re: Replacing tango.text.Ascii.isearch
On 25/10/2022 5:17 PM, Siarhei Siamashka wrote: Wow, I didn't expect anything like this and just thought that the nightmares of handling 8-bit codepages for non-English languages ceased to exist nowadays. Too bad. What are the best practices to deal with Turkish text in D language? std.uni doesn't support it. For casing it only supports the simple mappings which are 1:1 and not language dependent. I haven't got to it yet for my own string handling library, so I can't point you to that (even if it was not ready). I'm sure somebody has got it but you may end up wanting to use ICU unfortunately.
Re: Supporting foreach (k, v; T.init) for a user-defined (container) type
From there down: https://dlang.org/spec/statement.html#foreach_over_struct_and_classes
Re: How to use dub with ldc
If you only have one compiler available, dub will use it (doesn't matter if its dmd/ldc/gdc). rdmd is a tool that wraps dmd/ldc/gdc. https://github.com/dlang/tools/blob/master/rdmd.d If you only have ldc in your PATH variable, rdmd just "just work".
Re: Can someone tell me what the compiler thought I was trying to do?
On 19/10/2022 2:30 PM, H. S. Teoh wrote: On Wed, Oct 19, 2022 at 01:15:37AM +, Adam D Ruppe via Digitalmars-d-learn wrote: On Wednesday, 19 October 2022 at 00:57:31 UTC, H. S. Teoh wrote: Has it really been implemented? I tested the latest git master, the following code doesn't compile: it only applies to types, not to functions. Wat... so what's the use of it then? So it's not possible to mark the return value of an int function @mustUse without making, in theory, *all* ints @mustUse? I must confess I'm baffled as to the purpose of this strange design. Oh but it gets better: From C23 draft: The nodiscard attribute shall be applied to the identifier in a function declaration or to the definition of a structure, union, or enumeration type. If an attribute argument clause is present, it shall have the form: ( string-literal )
Re: Can someone tell me what the compiler thought I was trying to do?
https://github.com/dlang/dmd/blob/master/druntime/src/core/attribute.d#L292
Re: Find out what type my class is being converted to for comparisons
Well its not a type system issue.
Making u = n, that'll returns true.
So the problem almost certainly lies with IEEE-754.
They are horrible to compare (float/double).
Unfortunately you are stuck calling functions like isClose to compare.
https://dlang.org/phobos/std_math_operations.html#.isClose
Full code extracted from above:
```d
import std;
void main()
{
auto m = new Matrix!(2)();
m.data = [1.0, 0.0, 0.0, 1.0].dup;
auto n = new Matrix!(2)();
n.data = [2.0, 3.0, 4.0, 5.0].dup;
auto u = mult(m, n);
writeln("u.data vs n.data:");
for (int i = 0; i < u.data.length; ++i)
writeln(u.data[i], "\t", n.data[i]);
// using opEquals() directly is working, but it doesn't seem to be
being used
//assert(opEquals(u,n),"\"opEquals(u, n)\" is failing."); // this
works fine
assert(u == n, "\"u == n\" is failing."); // this fails. Why?
}
class Matrix(size_t X, size_t Y = X)
{
const size_t x_length = X;
const size_t y_length = Y;
double[X * Y] data;
/// both matrices have to have an identical shape to compare
/// each element must be identical to match
bool opEquals(size_t X, size_t Y)(const Matrix!(X, Y) m1, const
Matrix!(X, Y) m2)
{
for (int i = 0; i < m1.data.length; ++i)
if (m1.data[i] != m2.data[i])
return false;
return true;
}
}
```
Re: library to solve the system of linear equations
On 18/10/2022 9:37 AM, mw wrote: Maybe Mir should add static check for supported complier versions, rather than let user try and error. Dub has dependency checks for compiler/dub in it. It doesn't need to be in code.
Re: D Language Foundation Meeting September 2022 Monthly Meeting Summary
On 18/10/2022 3:10 AM, Mike Parker wrote: ### Iain Over the preceding month, Iain had little going on with D due to a personal situation. Most of the work he'd done had been on the infrastructure project and not on the compiler. He noted that I had migrated the dlang.org and dlang.io DNS servers to Cloudflare, and that several records had failed to transfer across (we had some other hiccups, but Iain, Vladimir Panteleev, Petar Kirov, and Mathias Lang, provided invaluable assistance in resolving those). We had managed to recover most of them. I wonder if this has anything to do with run.dlang.org is using a certificate for run.dlang.io for a while now (and hence not usable). But either way, awesome work everyone!
Re: Is it possible? branching on debug info
There is: D_Optimized https://dlang.org/spec/version.html#predefined-versions But nothing for debug info. I'm afraid I think you'll just have to use a version (unless you want to add it).
Re: How do I correctly install packages for use with Visual Studio?
On 17/10/2022 12:09 AM, Decabytes wrote: I'm trying to set up Visual Studio 2022 with Visual D, and I'm running into issues trying to get my project to build correctly. It's a double whammy because I've never used Visual Studio before (Just an Emacs Guy), but I need to debug my D programming and according to the [documentation](https://wiki.dlang.org/Debuggers) this is my only option on Windows. You don't need to develop with Visual Studio for native executables to debug using it. Build your program with debug symbols (-g) and open the executable as a project. You can then debug it with source code support.
Re: Replacing tango.text.Ascii.isearch
On 13/10/2022 9:55 PM, bauss wrote: Yeah, text isn't easy :D Indeed! It has me a bit concerned actually, I'm wondering if my string stuff will even work correctly for UI's due to performance issues. My string builder for instance allocates like crazy just to do slicing. But hey, at least I can feel confident that my general purpose allocator & infrastructure is working correctly!
Re: Replacing tango.text.Ascii.isearch
On 13/10/2022 9:42 PM, bauss wrote: Oh and to add onto this, IFF you have to do it the hacky way, then converting to uppercase instead of lowercase should be preferred, because not all lowercase characters can perform round trip, although a small group of characters, then using uppercase fixes it, so that's a relatively easy fix. A round trip is basically converting characters from one culture to another and then back. It's impossible with some characters when converting to lowercase, but should always be possible when converting to uppercase. You will want to repeat this process with normalize to NFKC and normalize to NFD before transforming. Otherwise there is a possibility that you will miss some transformations as the simplified mappings are 1:1 for characters and not everything is representable as a single character.
Re: Replacing tango.text.Ascii.isearch
On 13/10/2022 9:27 PM, bauss wrote: This doesn't actually work properly in all languages. It will probably work in most, but it's not entirely correct. Ex. Turkish will not work with it properly. Very interesting article: http://www.moserware.com/2008/02/does-your-code-pass-turkey-test.html Yes turkic languages, they require a state machine and quite a bit of LUTs to work correctly. You also need to provide a language and it has to operate on the whole string, not individual characters. I didn't think it was relevant since Ascii was in the original post ;)
Re: Visual D doesn't work, now Visual Studio Code / D doesn't work!!!! ....
Visual Studio with its c++ components can debug D code, it should not require Visual D to do so. Open executable as project. If this does not work, you have a serious issue in your system/VS install. This may help to narrow down what is going on.
Re: Is there a way to mark a dub package as linux only?
On 28/09/2022 7:18 AM, Alain De Vos wrote: Don't forget there is also BSD Should already be supported. Platform specific settings are supported through the use of field name suffixes. Suffixes are dash separated list of operating system/architecture/compiler identifiers, as defined in the D language reference, but converted to lower case. The order of these suffixes is os-architecture-compiler, where any of these parts can be left off. Additionally on Windows the architectures x86_omf and x86_mscoff can be used with dmd to differentiate between 32 bit object formats used with the --arch switch. Examples: https://dub.pm/package-format-json.html#build-settings
Re: Is there a way to mark a dub package as linux only?
Alternatively we could just extend platforms to work in places other than configurations. https://dub.pm/package-format-json.html#configuration-settings
Re: Detect uninitialized class var access
Currently in D you would be forced to create a vtable struct manually.
But if we had something like signatures you could do this:
```d
struct Foo {
//...
}
struct Bar {
InputRange input;
}
void doIt() {
Bar bar;
Foo* foo = new Foo;
bar.input = foo;
}
```
Classes are not the only way to do OOP :)
Re: Beerconf September 2022
Linkity link: https://meet.jit.si/Dlang2022SeptemberBeerConf
Re: Is this a new bug ?
```d
version(all) {
__gshared:
uint test2;
}
uint test;
```
Output with -vtls:
```
Up to 2.079.1: Success with output: onlineapp.d(9): test is thread
local
Since 2.080.1: Success with output: onlineapp.d(9): `test` is
thread local
```
Looks fine to me.
Re: Meanwhile on the audio front
Very nice and exciting! Congrats everyone.
Re: dub lint
https://github.com/dlang/dub/issues/2483
Re: Introducing alid
On 14/09/2022 8:44 PM, Ali Çehreli wrote: On 9/12/22 09:34, rikki cattermole wrote: > dub.json > errornogc/alid/errornogc.d > circularblocks/alid/circularblocks.d Considering I may want to let the users import the entire package as well with import alid; how can I achieve my goal of subpackages? Telling me to forget about subpackages altogether :) is an option because I've already spent hours trying to find my way through different directory structures, random dub.json edits, experimenting with ways of stopping dub from fetching and using the bad version of the repo repeatedly, and many other random things... In your root package you can still have the package.d file. You would use the version added by Dub to detect if you should public import the other modules. > DUB provides version identifier of dependencies for conditional compilation with version conditions. Have_ version identifier can be used for conditional compilation. https://dub.pm/advanced_usage
Re: Introducing alid
On 14/09/2022 2:48 PM, Salih Dincer wrote: I'm far from making a solid recommendation. Immutable with const still doesn't make sense to me. I claim we can live without them. Immutable confuses me a lot. I think we should take control by creating our own types. D Language should be unornamented. We have to have immutable. You need a way in a systems language to say that a given chunk of memory is read only to prevent accidental writes. Of course you are free to lie and say its mutable, but you can't lie to the cpu. It'll error if you try to write to it, resulting in the end of a process.
Re: Introducing alid
On 13/09/2022 4:25 AM, Ali Çehreli wrote: On 9/12/22 07:43, rikki cattermole wrote: Looks pretty well tested, nice! Thanks! Proud with 100% coverage. :) I was going to ask about coverage, that is awesome! But in other less nice things, I take it you did not test with GDC? GDC does not support cli args with the same names as dmd. One of these is -mv. So far, I started learning by copying arsd's dub.json. (Thank you, Adam! The misunderstandings are mine. :) ) It has the same issues, which is why I recommended against copying it. The file structure of subPackage/alid/subPackage will not require it and you will not have the cross import issues, where if you depend on errornogc you can also import (and then get linker errors) for circularblocks. If I understand you correctly, the directory structure need to be the following (also introducing src, which is clearly missing :)): alid/src/errornogc/alid/errornogc.d .../circularblocks/alid/circularblocks.d [...] No, you don't need the src directory, the subPackage directory functions as this. So: dub.json errornogc/alid/errornogc.d circularblocks/alid/circularblocks.d That'll work. Can I add a CI step to catch all such issues? It would be awesome if dub provided that. There is: https://github.com/dlang-community/setup-dlang But it doesn't look to support gdc or have been updated in a little while. Guess I need to start pinging people about it. Ali P.S. Another issue is function attributes seemingly used inaccurately but I asked that question on the 'learn' newsgroup already. Ping! ;) I have no solution to that unfortunately beyond template all the things.
Re: Introducing alid
Looks pretty well tested, nice! But in other less nice things, I take it you did not test with GDC? GDC does not support cli args with the same names as dmd. One of these is -mv. The file structure of subPackage/alid/subPackage will not require it and you will not have the cross import issues, where if you depend on errornogc you can also import (and then get linker errors) for circularblocks.
Re: OpenXR library bindings etc
Apart from not linking against OpenXR, I'm not seeing anything obviously wrong in that binding.
Re: Error "Unexpected '\n' when converting from type LockingTextReader to type int"
On 08/09/2022 11:24 AM, Synopsis wrote:
On Wednesday, 7 September 2022 at 23:06:44 UTC, rikki cattermole wrote:
Text in buffer: "123\n"
Read: "123"
Text in buffer: "\n"
Read: exception, expecting number for "\n"
Changing your readf format specifier to include the new line should work.
https://dlang.org/phobos/std_stdio.html#.File.readf
Thank you!
Adding the \n seems to solve my problem: ```readf("%s\n", )```
I have two further questions about this!
a- What is the difference with this syntax with the exclamation mark?
```readf!"%s\n"(f1.num);```
That is a template.
It'll type check that the format specifier matches your arguments.
https://tour.dlang.org/tour/en/basics/templates
b- Do I need to put ```/n``` in every readf statement? I mean,
considering that every input gets entered after pressing intro key (and
I guess this is what introduce the \n)
Yes.
Re: Error "Unexpected '\n' when converting from type LockingTextReader to type int"
Text in buffer: "123\n" Read: "123" Text in buffer: "\n" Read: exception, expecting number for "\n" Changing your readf format specifier to include the new line should work. https://dlang.org/phobos/std_stdio.html#.File.readf
Re: Reference to an unresolved external symbol
On 07/09/2022 10:14 PM, Injeckt wrote: On Wednesday, 7 September 2022 at 10:01:11 UTC, rikki cattermole wrote: You have probably forgotten to link against user32. I guess you right. But I don't know how i gonna link libs when I'm using "dmd main.d". Tell me please. I think it is as simple as adding user32.lib to dmd (directly).
Re: Reference to an unresolved external symbol
You have probably forgotten to link against user32.
Re: How to link a msvcr120.dll in an inverse recursive way after a Windows .exe binary deployment
I've been reading up fairly recently on RPATH for *nix which does what you want. Unfortunately as far as I've found there is no way to do this on Windows without an extra executable.
Re: Best practice for dub registry package and module names
I cannot recommend looking at how Adam has done it. I've been trying to get him to change it since he originally did it. It has known issues and yes it will still pull in all modules thanks to -I behavior except you get fun things like linker errors. Keep in mind, you are trying to optimize development & maintenance time associated with build & package management. Not optimize for quickest build times. So it isn't wasteful, you're just focusing on a different metric.
Re: Best practice for dub registry package and module names
Yeah you're over thinking this. It is a single dub package with a namespacing package directory.
Re: Best practice for dub registry package and module names
This slightly smells, single module dub packages. What does each module do?
Re: Constructors not working
I think you are wanting opAssign not opBinary. Also you made a mistake, since its a struct you don't want to new it when you construct and return it. ```d return new Time(secos / 3600, (secos % 3600) / 60, secos % 60); ``` Would be a ``Time*`` not ``Time`` which is what you returned.
Re: Disk write in a "for" loop with RwMutex never happens
On 30/08/2022 8:16 AM, Gavin Ray wrote: It must have been the "writing at end of file" bit? I don't know. It read like it should work. The offsets were correct, it just didn't work *shrug*.
Re: Disk write in a "for" loop with RwMutex never happens
After a bunch of playing around I managed to determine that it is as simple as the mode. exists(dbFileName) ? "r+" : "w+" Will fix it. Of course you shouldn't delete the file like that method is doing. It should probably reinitialize the FILE* descriptor.
Re: SAOC 2022 Projects
On 29/08/2022 11:46 PM, Mike Parker wrote: ### Lucian Danescu Lucian gave [his first DConf talk this year](https://youtu.be/ksNGwLTe0Ps?t=21650) on the subject of integrating DMD as a library with D-Scanner. And that's the project that he submitted, and that the judges accepted, for SAOC. To Lucian: If you need someone to ping for dlang-community side of things, I'm available @rikkimax for admin-y stuff.
Re: Beerconf August 2022
Its live! https://meet.jit.si/Dlang2022AugustBeerConf
Re: How to build DMD/Phobos on Windows
For dmd you use build.d that is in the repository.
For phobos win64.mak (used for 32bit by default as well):
"# Makefile to build D runtime library phobos{64,32mscoff}.lib for
Windows MSVC"
So MSVC make.
Beyond that idk, but its starting point (oh and druntime is now in dmd
repo, so ugh... yeah)
Re: Programs in D are huge
On 19/08/2022 4:56 AM, IGotD- wrote: BetterC means no arrays or strings library and usually in terminal tools you need to process text. Full D is wonderful for such task but betterC would be limited unless you want to write your own array and string functionality. Unicode support in Full D isn't complete. There is nothing in phobos to even change case correctly! Both are limited if you care about certain stuff like non-latin based languages like Turkic.
Re: my d blog has idea of effect system to replace @nogc etc
On 17/08/2022 3:05 AM, Guillaume Piolat wrote: On Tuesday, 16 August 2022 at 15:01:05 UTC, rikki cattermole wrote: But one key difference is it is designed to work with the GC even if it is -betterC @nogc @safe nothrow. How do you do that? Via dub's injectSourceFiles (that I added). https://github.com/Project-Sidero/basic_memory/blob/main/source/sidero/base/allocators/gc_hook.d https://github.com/Project-Sidero/basic_memory/blob/main/source/sidero/base/allocators/gc.d https://github.com/Project-Sidero/basic_memory/blob/main/source/sidero/base/allocators/locking.d#L111
Re: my d blog has idea of effect system to replace @nogc etc
And I'm building another. Allocators already working, tons of Unicode stuff implemented. Working on string builders atm. But one key difference is it is designed to work with the GC even if it is -betterC @nogc @safe nothrow.
Re: New WIP DUB documentation
It is pretty awesome, a lot easier to digest and get into!
Re: My programs issues
On 11/08/2022 12:36 AM, pascal111 wrote: 2) I used "goto", I heard from someone before that using "goto" isn't good programming feature. This is mostly a historical debate at this point. Back 40 years ago, goto wasn't typically limited within a procedure and doesn't have any checks in place to prevent you doing bad things. These days languages will implement such checks (including D). Some of the historical papers which debate this can be read from the book Literate Programming by Donald Knuth. If you do get the chance to read it, its a good read for cover to cover and teaches you a lot of the historical context that you may not get elsewhere. https://www.amazon.com/Literate-Programming-Lecture-Notes-Donald/dp/0937073806
Re: dirEntries() does not do source files *.d
Its working for me. [alpha@DESKTOP-RB97SA4 [/cygdrive/p/ProjectSidero/basic_memory/source/sidero/base/text/unicode$ rdmd --eval=$'import std; writeln(dirEntries(`.`, `*.d`, SpanMode.shallow));' [".\\casefold.d", ".\\casing.d", ".\\comparison.d", ".\\composing.d", ".\\defs.d", ".\\normalization.d", ".\\readonly.d", ".\\wordbreak."] Check what directory it is running in by called getcwd. https://dlang.org/phobos/std_file.html#getcwd
Re: Giving up
On 07/08/2022 10:45 AM, Walter Bright wrote: On 8/6/2022 1:29 PM, Timon Gehr wrote: Seems you should just use a long double/real literal? real x = 0x1p-16383L; // (works) Looks like that settles it. (Why didn't I notice that? Sheesh!) Needs a better error message. https://issues.dlang.org/show_bug.cgi?id=23284
Re: DConf 2022 pre+watch party!
Iain ended up creating a Jitsi room: https://meet.jit.si/Dconf2022OnlineBeerConf
Re: DConf 2022 pre+watch party!
On 01/08/2022 1:04 AM, Iain Buclaw wrote: How did this work out? :-) It has been low turn out so far, but since everything has had low amount of chatter that isn't too surprising. Shall we start a jitsi meet-up? I'm waiting to hear about the IRL beerconf, see if somebody will join in from there. If they do yeah we should.
Re: Obsecure problem 1
It is a pretty straight forward. You tried to access memory out of bounds of the slice. https://github.com/pascal111-fra/D/blob/main/dcollect.d#L34 That for loop is problematic in a number of ways. You should not use int, or uint to index into memory, only size_t should be used. It is an alias to either uint or ulong based upon the size of a pointer. ```d for(size_t i = ch.length - 1; i >= 0; i--) ``` Would be the corrected line. However, it is still not correct, what happens when ch.length is zero? It'll wrap around and become a very large number. That is most likely what happened here. To do this safely in D, use the foreach_reverse statement instead. There are very few reasons to use for loops in D. https://dlang.org/spec/statement.html#foreach-range-statement Adjusted: ```d foreach_reverse(i; 0 .. ch.length) ``` However this is not efficient as you are reallocating constantly. ```d char[] ch_rev; ch_rev.length = ch.length; size_t offset; foreach_reverse(c; ch) ch_rev[offset++] = c; ```
Re: "strtok" D equivalent
I don't know of a D version, although it should be pretty easy to write
up yourself.
But you can always use strtok itself.
https://github.com/dlang/dmd/blob/09d04945bdbc0cba36f7bb1e19d5bd009d4b0ff2/druntime/src/core/stdc/string.d#L97
Very similar to example given on the docs:
```d
void main()
{
import std.stdio, std.algorithm;
string input = "one + two * (three - four)!";
string delimiters = "!+-(*)";
foreach(value; input.splitWhen!((a, b) => delimiters.canFind(b))) {
writeln(value);
}
}
```
DConf 2022 pre+watch party!
Hello everyone! It is back, DConf IRL. To celebrate we will have a bit of a pre-party over in the Discord voice channel, as well as a bit of a watch party going on during the conference live streams. We may switch over to Jitsi later on depending on how the IRL BeerConf goes and if someone ends up joining from there. Discord invite link: https://discord.gg/bMZk9Q4 It all starts tomorrow, so stock up because it's going to be 6 days of D!
Re: "string" data type with readln
The version of readln you are using is[0]. This works by taking in a buffer of memory to write out, and returns how many codepoints were stored. Because you are not reusing memory, not using this form you can of course use string[1] instead, rather than ``char[]``. ```d string s = readln(); ``` The definition of string is[2]: ```d alias string = immutable(char)[]; ``` Note the immutable there, which means that each value in the slice cannot be modified. Hence why it can't be used as a buffer. [0] https://dlang.org/phobos/std_stdio.html#.readln.2 [1] https://dlang.org/phobos/std_stdio.html#.readln [2] https://github.com/dlang/dmd/blob/master/druntime/src/object.d#L69
Re: please help me to reverse a function call order
A bit more d-ified and uses foreach + foreach_reverse without allocating
an array.
```d
import std.stdio;
void main()
{
doRepetition(4, 3);
writeln("==");
doRepetitionReversed(4, 3);
}
void doRepetition(const int n, const int m)
{
// combination total number is m, element is repeatable.
assert(n >= 1 && n < 10);
assert(m >= 1 && m < 10);
enum N = 10;
ubyte[10] a;
void inc(int index, int r, int start, int end)
{
if (index == r)
{
// get one unique combination result, not repeatable
foreach (j; 0 .. r)
{
writef!"%d "(a[j]);
}
writeln;
return;
}
foreach (i; start .. end)
{
a[index] = cast(ubyte) i;
inc(index + 1, r, i, end);
}
}
inc(0, m, 0, n);
}
void doRepetitionReversed(const int n, const int m)
{
// combination total number is m, element is repeatable.
assert(n >= 1 && n < 10);
assert(m >= 1 && m < 10);
enum N = 10;
ubyte[10] a;
void inc(int index, int r, int start, int end)
{
if (index == r)
{
// get one unique combination result, not repeatable
foreach_reverse (j; 0 .. r)
{
writef!"%d "(a[j]);
}
writeln;
return;
}
foreach_reverse (i; start .. end)
{
a[index] = cast(ubyte) i;
inc(index + 1, r, i, end);
}
}
inc(0, m, 0, n);
}
```
Output:
```
0 0 0
0 0 1
0 0 2
0 0 3
0 1 1
0 1 2
0 1 3
0 2 2
0 2 3
0 3 3
1 1 1
1 1 2
1 1 3
1 2 2
1 2 3
1 3 3
2 2 2
2 2 3
2 3 3
3 3 3
==
3 3 3
3 3 2
3 2 2
2 2 2
3 3 1
3 2 1
2 2 1
3 1 1
2 1 1
1 1 1
3 3 0
3 2 0
2 2 0
3 1 0
2 1 0
1 1 0
3 0 0
2 0 0
1 0 0
0 0 0
```
Re: Beerconf July 2022
I've been getting a few pings about setting this up, so here it is: https://meet.jit.si/Dlang2022JulyBeerConf No password.
Re: Druntime merged into dmd repo
Very well done! I do hope this isn't the end, because things like bindings really shouldn't be in the dmd repository.
Re: The D Programming Language Vision Document
On 05/07/2022 11:49 PM, ryuukk_ wrote: Hopefully that includes proper built in Tagged Union, non OOP people need that otherwise we are stuck in C's era of programming C's era of programming also happens to coincide with ML which had tagged unions ;) The C family has never been very expressive.
Re: The D Programming Language Vision Document
On 04/07/2022 7:39 PM, Ola Fosheim Grøstad wrote: Yes, that is a common one that is maintained, but maybe there are BOOST licensed implementations too? One can do an exhaustive test for say two-character normalization against ICU to see if they are compliant. https://www.unicode.org/Public/14.0.0/ucd/NormalizationTest.txt My implementation passes this :3 It should be complete test cases.
Re: The D Programming Language Vision Document
On 04/07/2022 5:30 PM, Andrej Mitrovic wrote: Aren't these the polar opposites of each other? The GC is one of D's strengths, yet we should avoid it as much as possible in the standard library. Not necessarily. It could and should most likely mean that it won't do any heap allocations. Heap allocations are expensive after all.
Re: The D Programming Language Vision Document
We have a perfectly good Unicode handling library already. (Okay, little out of date and doesn't handle Turkic stuff, but fixable). The standard one is called ICU. Anyway, we are straying from my original point, that limiting ourselves to the string alias and not supporting wstring or dstring in Phobos is going to bite us. Its not what people expect, its not what we have supported and code that looks like it should work won't. There better be a good reason for this that isn't just removing templates.
Re: The D Programming Language Vision Document
On 04/07/2022 8:16 AM, Ola Fosheim Grøstad wrote: On Sunday, 3 July 2022 at 19:32:56 UTC, rikki cattermole wrote: It is required for string equivalent comparisons (which is what you should be doing in a LOT more cases! Anything user provided when compared should be normalized first. Well, I think it is reasonable for a protocol to require that the input is NFC, and just check it and reject it or call out to an external library to convert it into NFC. Anyway, UTF-8 is the only format that isn't affected by network byte order… So if you support more than UTF-8 then you have to support UTF-8, UTF16-LE, UTF16-BE, UTF-32LE, UTF-32BE… That is five formats for just a simple string… and only UTF-8 will be well tested by users. :-/ https://issues.dlang.org/show_bug.cgi?id=23186 We only support UTF-16/UTF-32 for the target endian. Text input comes from many sources, stdin, files and say the windowing system are three common sources that do not make any such guarantees.
Re: The D Programming Language Vision Document
On 04/07/2022 7:18 AM, Ola Fosheim Grøstad wrote: I hardly ever use anything outside UTF-8, and if I do then I use a well tested unicode library as it has to be correct and up to date to be useful. The utility of going beyond UTF-8 seems to be limited: https://en.wikipedia.org/wiki/UTF-32#Analysis I have just finished implementing string normalization which is based around UTF-32. It is required for string equivalent comparisons (which is what you should be doing in a LOT more cases! Anything user provided when compared should be normalized first.
Re: The D Programming Language Vision Document
On 04/07/2022 6:10 AM, Ola Fosheim Grøstad wrote: People who are willing to use 4 bytes per code point are probably using third party C-libraries that have their own representation, so you have to convert anyway? If you use Unicode and follow their recommendations, you are going to be using dstrings at some point. For example, string equivalence, and anything to do with case is going to use them and very likely to require multiple memory allocations to do it. Its just an unnecessary goal, when most of the string algorithms we have probably don't care about the encoding and those that do probably will be using dstrings.
Re: The D Programming Language Vision Document
> Stronger integration with other languages One of the things I judge D's compilers by is how well they can build a shared library. This is crucial for a lot of different applications of D and can be an complete stopper in using D if it doesn't "just work". To be blunt this is embarrassing, this should have been a top priority 10+ years ago... > Phobos and DRuntime I am very worried that this is going ahead without signatures. Its a major usability issue that concepts like ranges are not written into a function signature and is a common tripping point for people new to the language. I've been meaning to talk with Walter about this, this year. Times just haven't lined up at BeerConf to sort out lining up my designs into something that could actually go in. > No wstring or dstring. Any functions in Phobos v2 that deal with strings should deal exclusively with the string type. Users can convert from and to the other string types as needed. NOPEEE That's going to bite us big time when it comes to Unicode handling which wants to work with dstring's. > Provide automatic CI for actively-maintained third-party projects. I would like a big endian system to be included if possible, if a library is actively maintained you don't want surprises to arise from that.
