Re: How to use bootstrap with vibe.d.

2020-11-04 Thread James Blachly via Digitalmars-d-learn
On Wednesday, 4 November 2020 at 19:01:16 UTC, Alaindevos wrote: (title). In flask it is "from flask_bootstrap import Bootstrap". But what do you have to do with vibe.d ? I am not sure you really understand what bootstrap is?

Re: Does dmd's -i "include imported modules in the compilation" switch generate object files?

2020-11-04 Thread Jacob Carlborg via Digitalmars-d-learn
On 2020-11-03 20:02, H. S. Teoh wrote: I believe -i behaves as though you manually typed the names of the source files on the command line. So it would do what the compiler would usually do in the latter case. Yes, this is correct. AFAIK, that means it loads everything into memory and produ

How to use bootstrap with vibe.d.

2020-11-04 Thread Alaindevos via Digitalmars-d-learn
(title). In flask it is "from flask_bootstrap import Bootstrap". But what do you have to do with vibe.d ?

Re: Source code folder naming convention?

2020-11-04 Thread Dennis via Digitalmars-d-learn
On Wednesday, 4 November 2020 at 11:15:33 UTC, Vladimirs Nordholm wrote: Is there a "best practice" of what the source folder should be called? `dub init` creates a folder named `source`, so I would stick with that.

Re: Source code folder naming convention?

2020-11-04 Thread Mike Parker via Digitalmars-d-learn
On Wednesday, 4 November 2020 at 11:15:33 UTC, Vladimirs Nordholm wrote: Hello. Is there a "best practice" of what the source folder should be called? I commonly see either `source` or `src` in GitHub projects, but cannot find any formal best practice naming convention. dub looks for both

Source code folder naming convention?

2020-11-04 Thread Vladimirs Nordholm via Digitalmars-d-learn
Hello. Is there a "best practice" of what the source folder should be called? I commonly see either `source` or `src` in GitHub projects, but cannot find any formal best practice naming convention.