Re: Thoughts on function names containing arbitrary symbols

On 2011-10-05 04:40, Andrew Wiley wrote: On Tue, Oct 4, 2011 at 9:08 AM, Jacob Carlborg wrote: On 2011-10-04 12:37, Kagamin wrote: Jacob Carlborg Wrote: What are the thoughts around here on function names containing arbitrary symbols, like in Scala. Example: void ::: (int a) {} If D want

Re: Request for pre-review: std.serialization/orange

On 2011-10-05 03:49, Robert Jacques wrote: On Tue, 04 Oct 2011 12:54:27 -0400, Jacob Carlborg wrote: On 2011-10-04 17:14, Robert Jacques wrote: I'm sorry, you're right. In my mind b extended to the end of the a array, for some reason. However, if you do define b to extend to the end of the a

Re: std.getopt suggestion

On 2011-10-04 21:39, Andrei Alexandrescu wrote: On 10/4/11 12:46 PM, Jacob Carlborg wrote: On 2011-10-04 17:48, Andrei Alexandrescu wrote: On 10/04/11 09:09, Jacob Carlborg wrote: On 2011-10-04 13:21, Regan Heath wrote: In this particular case, because these std,.getopt options are global var

Re: Thread local and memory allocation

On Tue, 04 Oct 2011 23:56:52 -0400, Andrew Wiley wrote: On Tue, Oct 4, 2011 at 10:55 PM, Andrew Wiley wrote: On Tue, Oct 4, 2011 at 8:59 PM, Robert Jacques wrote: On Tue, 04 Oct 2011 10:54:58 -0400, Andrew Wiley wrote: On Tue, Oct 4, 2011 at 3:52 AM, Walter Bright wrote: On 10/4/2011

Re: Garbage collection book

On 10/4/2011 11:06 PM, Andrei Alexandrescu wrote: http://www.amazon.com/Garbage-Collection-Handbook-Management-Algorithms/dp/1420082795/ref=sr_1_1?s=books&ie=UTF8&qid=1317790242&sr=1-1 I heard it's good. I have the older version: http://www.amazon.com/exec/obidos/ASIN/0471941484/classicempi

Re: Thread local and memory allocation

On Tue, 04 Oct 2011 23:55:19 -0400, Andrew Wiley wrote: On Tue, Oct 4, 2011 at 8:59 PM, Robert Jacques wrote: On Tue, 04 Oct 2011 10:54:58 -0400, Andrew Wiley wrote: On Tue, Oct 4, 2011 at 3:52 AM, Walter Bright wrote: On 10/4/2011 1:22 AM, deadalnix wrote: Do you mean manage the mem

Re: Thread local and memory allocation

deadalnix: > This is why the type system is made for isn't it ? Casts are often the points where type systems fail :-) Bye, bearophile

Garbage collection book

http://www.amazon.com/Garbage-Collection-Handbook-Management-Algorithms/dp/1420082795/ref=sr_1_1?s=books&ie=UTF8&qid=1317790242&sr=1-1 I heard it's good. Andrei

Re: Thoughts on function names containing arbitrary symbols

Am 05.10.2011, 04:40 Uhr, schrieb Andrew Wiley : On Tue, Oct 4, 2011 at 9:08 AM, Jacob Carlborg wrote: On 2011-10-04 12:37, Kagamin wrote: Jacob Carlborg Wrote: What are the thoughts around here on function names containing arbitrary symbols, like in Scala. Example: void ::: (int a) {}

Re: std.getopt suggestion

Am 05.10.2011, 03:28 Uhr, schrieb Jonathan M Davis : On Wednesday, October 05, 2011 02:51:47 Andrej Mitrovic wrote: Yeah I've never seen --abc used as -a -b -c before, it looks quite strange to me. Is this common in unixland? In unix land, the normal situation is that -- denotes a flag with o

Re: Thread local and memory allocation

On Tue, Oct 4, 2011 at 10:55 PM, Andrew Wiley wrote: > On Tue, Oct 4, 2011 at 8:59 PM, Robert Jacques wrote: >> On Tue, 04 Oct 2011 10:54:58 -0400, Andrew Wiley >> wrote: >> >>> On Tue, Oct 4, 2011 at 3:52 AM, Walter Bright >>> wrote: On 10/4/2011 1:22 AM, deadalnix wrote: > >

Re: Thread local and memory allocation

On Tue, Oct 4, 2011 at 8:59 PM, Robert Jacques wrote: > On Tue, 04 Oct 2011 10:54:58 -0400, Andrew Wiley > wrote: > >> On Tue, Oct 4, 2011 at 3:52 AM, Walter Bright >> wrote: >>> >>> On 10/4/2011 1:22 AM, deadalnix wrote: Do you mean manage the memory that way : Shared heap -> TL

Re: Exchange of possible interest :o)

On 10/4/11 9:50 PM, Caligo wrote: On Tue, Oct 4, 2011 at 5:53 PM, Andrei Alexandrescu mailto:seewebsiteforem...@erdani.org>> wrote: http://gcc.gnu.org/ml/gcc/__2011-10/msg00037.html Andrei Does this mean D will be part of GCC 4.7?

Re: Exchange of possible interest :o)

On Tue, Oct 4, 2011 at 5:53 PM, Andrei Alexandrescu < seewebsiteforem...@erdani.org> wrote: > http://gcc.gnu.org/ml/gcc/**2011-10/msg00037.html > > Andrei > Does this mean D will be part of GCC 4.7?

Re: Thoughts on function names containing arbitrary symbols

On Tue, Oct 4, 2011 at 9:08 AM, Jacob Carlborg wrote: > On 2011-10-04 12:37, Kagamin wrote: >> >> Jacob Carlborg Wrote: >> >>> What are the thoughts around here on function names containing arbitrary >>> symbols, like in Scala. Example: >>> >>> void ::: (int a) {} >> >> If D wants to be FP-style,

Re: Thread local and memory allocation

On Tue, 04 Oct 2011 10:54:58 -0400, Andrew Wiley wrote: On Tue, Oct 4, 2011 at 3:52 AM, Walter Bright wrote: On 10/4/2011 1:22 AM, deadalnix wrote: Do you mean manage the memory that way : Shared heap -> TL pool within the shared heap -> allocation in thread from TL pool. And complete GC

Re: Thread local and memory allocation

On Tue, 04 Oct 2011 17:50:03 -0400, deadalnix wrote: Le 04/10/2011 08:02, Robert Jacques a écrit : On Mon, 03 Oct 2011 15:48:57 -0400, deadalnix wrote: [snip] What I suggest in add a flag SHARED in BlkAttr and store it as an attribute of the block. Later modification could be made according

Re: Request for pre-review: std.serialization/orange

On Tue, 04 Oct 2011 12:54:27 -0400, Jacob Carlborg wrote: On 2011-10-04 17:14, Robert Jacques wrote: I'm sorry, you're right. In my mind b extended to the end of the a array, for some reason. However, if you do define b to extend to the end of the a array, then it can append without allocating

Dupe checker

A little Go-Ruby comparison I've found through Reddit, with a chance to show a D version too: http://blog.carbonfive.com/2011/10/04/explorations-in-go-a-dupe-checker-in-go-and-ruby/ http://blog.carbonfive.com/2011/10/04/explorations-in-go-a-dupe-checker-in-go-and-ruby/ Bye, bearophile

Re: std.getopt suggestion

On Tuesday, October 04, 2011 20:28:30 Andrei Alexandrescu wrote: > On 10/4/11 7:51 PM, Andrej Mitrovic wrote: > > Yeah I've never seen --abc used as -a -b -c before, it looks quite > > strange to me. Is this common in unixland? > > No, but bundling -abc as -a -b -c is quite common, particularly in

Re: std.getopt suggestion

On 10/4/11 7:51 PM, Andrej Mitrovic wrote: Yeah I've never seen --abc used as -a -b -c before, it looks quite strange to me. Is this common in unixland? No, but bundling -abc as -a -b -c is quite common, particularly in older programs. Andrei

Re: std.getopt suggestion

On Wednesday, October 05, 2011 02:51:47 Andrej Mitrovic wrote: > Yeah I've never seen --abc used as -a -b -c before, it looks quite > strange to me. Is this common in unixland? In unix land, the normal situation is that -- denotes a flag with one or more characters in it, whereas - denotes a flag

Re: std.getopt suggestion

Yeah I've never seen --abc used as -a -b -c before, it looks quite strange to me. Is this common in unixland?

Exchange of possible interest :o)

http://gcc.gnu.org/ml/gcc/2011-10/msg00037.html Andrei

Re: std.getopt suggestion

Am 04.10.2011, 22:41 Uhr, schrieb Andrei Alexandrescu : does -in mean --in or -i -n? This case must be prohibited and exorcised. You should decide to either use bundling of -i -n to -in *or* use single dash long arguments. DMD does *not* allow -wv for example although both letters are va

Re: Thread local and memory allocation

Le 04/10/2011 08:02, Robert Jacques a écrit : On Mon, 03 Oct 2011 15:48:57 -0400, deadalnix wrote: [snip] What I suggest in add a flag SHARED in BlkAttr and store it as an attribute of the block. Later modification could be made according to this flag. This attribute shouldn't be modifiable l

Re: std.getopt suggestion

On 10/4/11 3:10 PM, Christophe wrote: Andrei Alexandrescu , dans le message (digitalmars.D:146070), a écrit : On 10/4/11 2:39 PM, Andrei Alexandrescu wrote: On 10/4/11 12:05 PM, Christophe wrote: Andrej Mitrovic , dans le message (digitalmars.D:146060), a écrit : I'm don't often use getopt ju

Re: std.getopt suggestion

On 10/4/11 12:05 PM, Christophe wrote: Andrej Mitrovic , dans le message (digitalmars.D:146060), a écrit : I'm don't often use getopt just for the fact that I can't use single-dash arguments like '-release'. DMD uses this syntax, and so to other tools. It's not a big deal thanks to D's fantastic

Re: std.getopt suggestion

Andrei Alexandrescu , dans le message (digitalmars.D:146070), a écrit : > On 10/4/11 2:39 PM, Andrei Alexandrescu wrote: >> On 10/4/11 12:05 PM, Christophe wrote: >>> Andrej Mitrovic , dans le message (digitalmars.D:146060), a écrit : I'm don't often use getopt just for the fact that I can't u

Re: std.getopt suggestion

On 10/4/11 2:39 PM, Andrei Alexandrescu wrote: On 10/4/11 12:05 PM, Christophe wrote: Andrej Mitrovic , dans le message (digitalmars.D:146060), a écrit : I'm don't often use getopt just for the fact that I can't use single-dash arguments like '-release'. DMD uses this syntax, and so to other to

Re: std.getopt suggestion

On 10/4/11 12:46 PM, Jacob Carlborg wrote: On 2011-10-04 17:48, Andrei Alexandrescu wrote: On 10/04/11 09:09, Jacob Carlborg wrote: On 2011-10-04 13:21, Regan Heath wrote: In this particular case, because these std,.getopt options are global variables, building something which uses them, or st

Re: std.getopt suggestion

Andrej Mitrovic , dans le message (digitalmars.D:146060), a écrit : > I'm don't often use getopt just for the fact that I can't use > single-dash arguments like '-release'. DMD uses this syntax, and so to > other tools. It's not a big deal thanks to D's fantastic > string-manipulation abilities, so

Re: Thread local and memory allocation

On 10/4/2011 2:32 AM, deadalnix wrote: Le 04/10/2011 10:52, Walter Bright a écrit : Allocate an object, then cast it to immutable, and pass it to another thread. That is explicitly said to be unsafe on D's website. As long as a reference exist in the creating thread, this should work, but if

Re: The problem with std.conv.emplace

Timon Gehr wrote: > On 04.10.2011 08:05, Benjamin Thaut wrote: >> I'm currently trying to fix the problem I have with std.conv.emplace to >> fully replace the deprecated new/delete operator overloading with a >> template. >> However it discovered that this is currently not possible, at least not >

Re: Request for pre-review: std.serialization/orange

On 2011-10-04 17:14, Robert Jacques wrote: I'm sorry, you're right. In my mind b extended to the end of the a array, for some reason. However, if you do define b to extend to the end of the a array, then it can append without allocating: auto a = [0, 1, 2, 3, 4]; auto b = a[2 .. $]; b ~= 5; asse

Re: std.getopt suggestion

On 10/4/2011 2:55 AM, Jacob Carlborg wrote: They at least removed export templates. True. I know there were some adamant defenders of it in the past, but I don't know if anyone defended it this time. A difference from trigraphs is that export was implemented by only one vendor, and every othe

Re: std.getopt suggestion

On 2011-10-04 17:48, Andrei Alexandrescu wrote: On 10/04/11 09:09, Jacob Carlborg wrote: On 2011-10-04 13:21, Regan Heath wrote: In this particular case, because these std,.getopt options are global variables, building something which uses them, or std.getopt will introduce side effects to othe

Re: std.getopt suggestion

I'm don't often use getopt just for the fact that I can't use single-dash arguments like '-release'. DMD uses this syntax, and so to other tools. It's not a big deal thanks to D's fantastic string-manipulation abilities, so I just roll my own. All I need is a switch(args) statement.

Re: Names with trailing question mark

bearophile Wrote: > contains? > areInside ==> inside? > > > I don't remember serious recent discussions here about that last form. > Allowing a single trailing question mark in D names has some advantages: > > 1) It gives a standard way to denote a predicate, so it becomes very easy to > tell

Re: Request for pre-review: std.serialization/orange

On Tue, 04 Oct 2011 03:22:35 -0400, Jacob Carlborg wrote: On 2011-10-04 07:21, Robert Jacques wrote: [snip] Actually it does not need to be part of the public API when I think about it. I can move it into Serializer. Array would still need to be public since both Serailzer and Archive need a

Re: Thread local and memory allocation

On Tue, Oct 4, 2011 at 3:52 AM, Walter Bright wrote: > On 10/4/2011 1:22 AM, deadalnix wrote: >> >> Do you mean manage the memory that way : >> Shared heap -> TL pool within the shared heap -> allocation in thread from >> TL pool. >> >> And complete GC collect. > > Yes. > > >> This is a good solut

Re: std.getopt suggestion

On 10/04/11 09:09, Jacob Carlborg wrote: On 2011-10-04 13:21, Regan Heath wrote: In this particular case, because these std,.getopt options are global variables, building something which uses them, or std.getopt will introduce side effects to other uses of std.getopt. Meaning the current design

Re: Names with trailing question mark

Jacob Carlborg , dans le message (digitalmars.D:146055), a écrit : > > I would say it would be illegal and that the ternary operator requires a > space before the question mark. It works like this in Ruby as well. It > would be parsed like this: > > (foo?) + (foo?(a)) : b > > Have a look at: h

Re: Names with trailing question mark

On 2011-10-04 15:03, Timon Gehr wrote: On 04.10.2011 01:37, bearophile wrote: Predicates are quite common. In D I presume the standard way to write them is with a name like "isFoo". In other languages they are written in other ways: if (foo.isEven) {} if (foo.isEven()) {} filter!isEven(data)

Re: std.getopt suggestion

On 2011-10-04 13:21, Regan Heath wrote: On Tue, 04 Oct 2011 05:20:48 +0100, Walter Bright wrote: I've been only a casual user of std.getopt, barely scratching the surface of what it can do. But I do have a few general thoughts on this. One of the very hardest things in design is knowing when t

Re: Names with trailing question mark

On 2011-10-04 16:03, Jacob Carlborg wrote: On 2011-10-04 12:12, Christophe wrote: I don't really like this idea. D has limitations to accepted symbol that are strict, but handy in many cases. Accepting strange character in a method name can lead to parsing ambiguities and I like the way D enfor

Re: Names with trailing question mark

On 2011-10-04 12:12, Christophe wrote: I don't really like this idea. D has limitations to accepted symbol that are strict, but handy in many cases. Accepting strange character in a method name can lead to parsing ambiguities and I like the way D enforce non-ambiguous code. I understand why we c

Re: Names with trailing question mark

On 2011-10-04 12:22, Gor Gyolchanyan wrote: Here's what i suggest to do: struct MyTestStruct { int[] array; // opCond must take at least a single string template parameter and exactly two lazy parameters, second of which may have a default value. T opCond(string name : "empty", T

Re: Thoughts on function names containing arbitrary symbols

On 2011-10-04 12:37, Kagamin wrote: Jacob Carlborg Wrote: What are the thoughts around here on function names containing arbitrary symbols, like in Scala. Example: void ::: (int a) {} If D wants to be FP-style, it definitely must adopt cryptic FP naming conventions or it would be not true F

D ABI tricks.

I was creating a ultra-fast dynamic method call mechanism when i realized, that I'm (ab)using D's standard ABI, which would also be interesting to use when dealing with functions. Particularly, interesting is the way parameter storage classes can be safely removed from the function without any chan

Re: The problem with std.conv.emplace

On 04.10.2011 08:05, Benjamin Thaut wrote: I'm currently trying to fix the problem I have with std.conv.emplace to fully replace the deprecated new/delete operator overloading with a template. However it discovered that this is currently not possible, at least not to my knowdelge. The problem is

Re: Names with trailing question mark

On 04.10.2011 01:37, bearophile wrote: Predicates are quite common. In D I presume the standard way to write them is with a name like "isFoo". In other languages they are written in other ways: if (foo.isEven) {} if (foo.isEven()) {} filter!isEven(data) if (foo.evenQ) {} if (foo.evenQ()) {} f

Re: std.getopt suggestion

On Tue, 04 Oct 2011 05:20:48 +0100, Walter Bright wrote: I've been only a casual user of std.getopt, barely scratching the surface of what it can do. But I do have a few general thoughts on this. One of the very hardest things in design is knowing when to say "no" to a new feature. The fea

Re: Thoughts on function names containing arbitrary symbols

Jacob Carlborg Wrote: > What are the thoughts around here on function names containing arbitrary > symbols, like in Scala. Example: > > void ::: (int a) {} If D wants to be FP-style, it definitely must adopt cryptic FP naming conventions or it would be not true FP.

Re: Names with trailing question mark

Here's what i suggest to do: struct MyTestStruct { int[] array; // opCond must take at least a single string template parameter and exactly two lazy parameters, second of which may have a default value. T opCond(string name : "empty", T)(lazy T yes, lazy T no = T.init) { i

Re: Names with trailing question mark

> auto mts.empty ? "wonderful" : "awful"; > auto mts.empty ? "awesome"; sorry, a typo: auto a0 = mts.empty ? "wonderful" : "awful"; auto a1 = mts.empty ? "awesome"; struct MyTestStruct { int[] array; // "this" as a template parameter will make the condition apply to the class

Re: std.getopt suggestion

On 2011-10-04 11:02, Walter Bright wrote: On 10/4/2011 1:06 AM, Nick Sabalausky wrote: "Walter Bright" wrote in message news:j6e1k9$2p9u$1...@digitalmars.com... 2. Once a feature is there, it stays forever. It's very hard to judge how many people rely on a feature that turns out in hindsight t

Re: Names with trailing question mark

I don't really like this idea. D has limitations to accepted symbol that are strict, but handy in many cases. Accepting strange character in a method name can lead to parsing ambiguities and I like the way D enforce non-ambiguous code. I understand why we can think that the question mark is ni

Thoughts on function names containing arbitrary symbols

What are the thoughts around here on function names containing arbitrary symbols, like in Scala. Example: void ::: (int a) {} -- /Jacob Carlborg

Re: Thoughts on function names containing arbitrary symbols

Le 04/10/2011 11:46, Jacob Carlborg a écrit : What are the thoughts around here on function names containing arbitrary symbols, like in Scala. Example: void ::: (int a) {} That would only promote unreadable code and complexify the parsing (actually, you see that as complexification of the pa

Re: Thread local and memory allocation

Le 04/10/2011 10:52, Walter Bright a écrit : Allocate an object, then cast it to immutable, and pass it to another thread. That is explicitly said to be unsafe on D's website. As long as a reference exist in the creating thread, this should work, but if thoses references disapears, you'll en

Re: std.getopt suggestion

On 10/4/2011 1:06 AM, Nick Sabalausky wrote: "Walter Bright" wrote in message news:j6e1k9$2p9u$1...@digitalmars.com... 2. Once a feature is there, it stays forever. It's very hard to judge how many people rely on a feature that turns out in hindsight to be baggage. If people are relying on i

Re: std.getopt suggestion

On 10/3/2011 11:11 PM, Nick Sabalausky wrote: Steve Jobs is famous for handling the bare minimum that works for 90% of *average Joe* users and saying "Fuck off" to everyone and everything else. That's why all his products are shit. On the other hand, D makes no attempt at a "walled garden". Nob

Re: Thread local and memory allocation

On 10/4/2011 1:22 AM, deadalnix wrote: Do you mean manage the memory that way : Shared heap -> TL pool within the shared heap -> allocation in thread from TL pool. And complete GC collect. Yes. This is a good solution do reduce contention on allocation. But a very different thing than I wa

Re: Names with trailing question mark

On 2011-10-04 10:28, bearophile wrote: Jacob Carlborg: if (foo.even()?) Why would you put the question mark after the parentheses. At least in Ruby the question mark is part of the method name. This looks better: if (foo.even?()) It's a typo of mine, sorry :-) The question mark is part of

Re: Names with trailing question mark

Jacob Carlborg: > > if (foo.even()?) > > Why would you put the question mark after the parentheses. At least in > Ruby the question mark is part of the method name. This looks better: > > if (foo.even?()) It's a typo of mine, sorry :-) The question mark is part of the name, so it is of course

Re: Thread local and memory allocation

Le 04/10/2011 02:15, Walter Bright a écrit : On 10/3/2011 4:20 PM, Sean Kelly wrote: Immutable data would have to be allocated on the shared heap as well, which means the contention for the shared heap may actually be fairly significant. But the alternatives are all too complex (migrating immuta

Re: std.getopt suggestion

"Walter Bright" wrote in message news:j6e1k9$2p9u$1...@digitalmars.com... > > 2. Once a feature is there, it stays forever. It's very hard to judge how > many people rely on a feature that turns out in hindsight to be baggage. If people are relying on it, is it really baggage? > It's why I hav

Re: Request for pre-review: std.serialization/orange

On 2011-10-04 07:21, Robert Jacques wrote: That putting isSliceOf in the public API, implies its usage by the archiver. Ok, then I'll remove it. Actually it does not need to be part of the public API when I think about it. I can move it into Serializer. Array would still need to be public sin