On Friday, 19 February 2016 at 04:02:02 UTC, Craig Dillabaugh
wrote:
Would you be interested in mentoring a student for the Google
Summer of Code to do work on std.xml?
Yes, why not!
On Thursday, 18 February 2016 at 18:28:10 UTC, Alex Vincent wrote:
Regarding control characters: If you give me a complete sample
file, I can run it through Mozilla's UTF stream conversion
and/or XML parsing code (via either SAX or DOMParser) to tell
you how that reacts as a reference.
On Thursday, 18 February 2016 at 16:54:10 UTC, Robert burner
Schadek wrote:
unix file says it is a utf8 encoded file, but not BOM is
present.
the hex dump is "3C 66 6F 6F 3E C2 80 3C 2F 66 6F 6F 3E"
On Thursday, 18 February 2016 at 16:47:35 UTC, Adam D. Ruppe
wrote:
On Thursday, 18 February 2016 at 16:41:52 UTC, Robert burner
Schadek wrote:
for instance, quick often I find <80> in tests that are
supposed to be valid xml 1.0. they are invalid xml 1.1 though
What char encoding does the
for instance, quick often I find <80> in tests that are supposed
to be valid xml 1.0. they are invalid xml 1.1 though
While working on a new xml implementation I came cross "control
characters (CC)". [1]
When trying to validate/convert an utf string these lead to
exceptions, because they are not valid utf character.
Unfortunately, some of these characters are allowed to appear in
valid xml 1.* documents.
I
On Thursday, 18 February 2016 at 12:30:29 UTC, Andrei
Alexandrescu wrote:
also I would like to see this
https://github.com/D-Programming-Language/phobos/pull/2995 go
in first
to be able to accurately measure and compare performance
Would the measuring be possible with 2995 as a dub package?
On Thursday, 18 February 2016 at 10:18:18 UTC, Robert burner
Schadek wrote:
If you want to on some XML stuff, please join me. It is
properly more productive working together than creating two
competing implementations.
also I would like to see this
On Thursday, 18 February 2016 at 04:34:13 UTC, Alex Vincent wrote:
I'm looking for a status update. DUB doesn't seem to have many
options posted. I was thinking about starting a SAXParser
implementation.
I'm working on it, but recently I had to do some major
restructuring of the code.
Yes, something like that would be nice. But as the website states
you need to use maven to build the project that uses that library.
I can only suspect, but I think they use maven to collect all
functions that use @Benchmark. And this leads to the problem the
unittest library proposal for
On Thursday, 14 January 2016 at 07:44:16 UTC, Jacob Carlborg
wrote:
std.experimental.memory with submodules for the different use
cases:
std.experimental.memory.rc
std.experimental.memory.gc
std.experimental.memory.manual // or something
this has my vote
I guess the first submodule should
congratulations
On Tuesday, 5 January 2016 at 02:44:48 UTC, sanjayss wrote:
I'm doing the following:
import std.experimental.logger;
int
main(string[] args)
{
sharedLog = new FileLogger("logfile.log");
log("Test log 1");
log("Test log 2");
log("Test log 3");
}
diff:
sharedLog = new
On Tuesday, 5 January 2016 at 16:34:27 UTC, Dicebot wrote:
BTW, the default implementation is a direct result of the "by
default multi-threading safe" requirement brought up multiple
times during reviews.
.. this remains a concern. I know that with some tweaks and lot
of custom overriding
On Sunday, 3 January 2016 at 21:37:28 UTC, Dicebot wrote:
Haven't found any issues with std.allocator so far but
std.logger definitely is not Phobos ready per my requirements.
I have been recently re-evaluating it as possible replacement
for old Tango logger we use and found that in several
On Monday, 4 January 2016 at 10:58:09 UTC, Jonathan M Davis wrote:
If I understand correctly (based on previous statements by
Dicebot), the problem is that at Sociomantic, they reuse
buffers heavily. So, they basically don't use string much of
anywhere and instead use some combination of
As talk is cheap, here is the code:
http://dpaste.dzfl.pl/ba4df05339f6
not 20 lines but for 99 lines you get two Loggers and some tests.
Yes the cast is ugly, but then I'm writing dynamic content into
stack arrays.
I actually have a patch in the pipeline for this,. That patch
require to change the protection for beginLogMsg, logMsgPart,
finishLogMsg from protected to public and bye bye cast.
logMsgPart already takes a
On Tuesday, 29 December 2015 at 16:11:00 UTC, Ilya Yaroshenko
wrote:
OK, lets discuss every function.
That is acceptably the problem. It is not about the documentation
of the functions it is about the documentation binding the
functions together and the documentation giving the idea of the
On Monday, 28 December 2015 at 18:39:47 UTC, Ilya Yaroshenko
wrote:
Have you read the latest changes?
http://forum.dlang.org/post/djgkkrdufycyjhpma...@forum.dlang.org
I have.
The problem with the doc is that is describes what it can be used
for, but it does not describe what it is.
It is
On Monday, 28 December 2015 at 07:11:00 UTC, Jack Stouffer wrote:
The final tally:
Yes: 12
No: 0
This is not true, my yes was conditional and the documentation is
still weak. So it is
Yes: 11
Yes: Conditional
No: 0
Please do not merge this with the current state of documentation.
On Monday, 28 December 2015 at 15:52:09 UTC, Robert burner
Schadek wrote:
fix
Yes: 11
Yes: Conditional: 1 <<-- fix here
No: 0
Please do not merge this with the current state of
documentation.
Update:
It now also generates functions that call the vibe.d rest service
in typestrict.
On Wednesday, 16 December 2015 at 17:49:03 UTC, Ilya Yaroshenko
wrote:
* Miscellaneous
** string mixins. I think some of the string mixins can be
removed for something more readable/debuggable
**
I have not found examples where string mixins can be removed.
Please refer to particular
On Wednesday, 16 December 2015 at 17:49:03 UTC, Ilya Yaroshenko
wrote:
In the same time I expect few articles from another engineers
about ndslice like this http://dlang.org/intro-to-datetime.html
. It is much better to have explanation from different
engineers.
Please no, put all the doc
Yes with many conditions:
* Documentation
** The documentation needs a complete rewrite. If I hadn't had
any prior knowledge, I would have needed to read the numpy
documentation to figure what this package does. That is not
acceptable. It is also not clear how the functionally in the
package
dstructtotypescript is a program that created typescript
interfaces/enums out of D
structs/enums.
https://github.com/burner/dstructtotypescript
The web framework vibe.d was very good at serializing data into
json.
Typescript allows the user to have a typed version of
javascript. Which means
On Saturday, 12 December 2015 at 22:57:55 UTC, Ola Fosheim
Grøstad wrote:
2. Debug-mode testing of integer overflow.
https://github.com/D-Programming-Language/phobos/pull/3389
wonderful!
I couldn't easily find how to make the module work with
allocators. IMO combining this module with
std.experiemtal.allocator should be possible. And if it is
already possible, there should be tests for documentation and
validation.
On Friday, 13 November 2015 at 02:50:07 UTC, Daniel Murphy wrote:
You also need to modify root/rmem.d to actually use the GC as
the allocator.
I should have known that it couldn't be that simple. Anyway,
after doing so. Building druntime and phobos die with a segfault,
but all dmd tests
On Wednesday, 11 November 2015 at 13:47:27 UTC, Johannes Pfau
wrote:
A quick workaround could be enabling the GC for DDMD. IIRC I
read somewhere on github that the segfaulting code was actually
rewritten now and the GC might just work.
I just run make -f posix.mak unittest -j10 on phobos
druntime also works with GC activated
https://github.com/burner/std.xml2 2016
On Wednesday, 4 November 2015 at 14:20:56 UTC, tester wrote:
no killer feature and as interesting as brainfuck
Next time, instead of pointing to the changelog, I have to write
the article for them. Anyway, better than nothing.
On Wednesday, 4 November 2015 at 16:07:11 UTC, Andrei
Alexandrescu wrote:
On 11/4/15 3:20 PM, tester wrote:
in essence:
no killer feature and as interesting as brainfuck
Was this a comment in the article? I didn't see it. -- Andrei
no, it is the summary of the article by tester
On Wednesday, 28 October 2015 at 00:28:51 UTC, Andrei
Alexandrescu wrote:
We have examples from the past when additions that seemed
obvious and sensible needed a few tweaks before stabilization.
Could you list them please.
I do not like the idea.
1. Whenever I look into "learn" I get the
On Tuesday, 27 October 2015 at 02:45:24 UTC, Andrei Alexandrescu
wrote:
Normally we'd be holding this on the forum, but as we all know,
forum discussions tend to meander a lot and lose focus. For
that reason, please write me email about joining a mailing list
dedicated to discussions on
On Tuesday, 27 October 2015 at 09:48:21 UTC, Andrei Alexandrescu
wrote:
So I'll add you to the list then.
Acknowledged
Voting Result:
Yes: 1
Conditional Yes: 1
No: 3
Therefore, std.experimental.testing is rejected in the current
state.
On Wednesday, 21 October 2015 at 11:05:12 UTC, Andrei
Alexandrescu wrote:
I'm finally getting the cycles to get to thinking about Design
by Introspection containers.
What do you have in mind about the Design by Introspection (DyI,
DbI is taken) for the container?
How do you plan to use the
On Wednesday, 21 October 2015 at 14:20:23 UTC, Andrei
Alexandrescu wrote:
Containers will obey subsets of a nomenclature of primitives.
Just to be crystal clear, something like this?
void fun(Container)(ref Container c) if (hasAppend!Container) {
// append stuff to c
}
On Wednesday, 21 October 2015 at 20:06:41 UTC, Andrei
Alexandrescu wrote:
"More Catholic than the Pope" = overdoing something all too
pedantically. What I mean is: let's get things started and if
there's any need for isXxx we'll add them. -- Andrei
+1
On Wednesday, 21 October 2015 at 17:23:15 UTC, Andrei
Alexandrescu wrote:
Even simpler, hasMethod!(Container, "append") -- Andrei
I know this goes against your talk at DConf, but having to write
string parameters does not feel good. I'm will properly not be
the only one who will mistype
On Thursday, 15 October 2015 at 10:33:11 UTC, Andrei Alexandrescu
wrote:
On 10/15/15 10:51 AM, Robert burner Schadek wrote:
On Thursday, 15 October 2015 at 05:47:16 UTC, Andrei
Alexandrescu wrote:
Brian, should we add you? LMK. -- Andrei
indeed!
Dunn. -- Andrei
nice
On Thursday, 15 October 2015 at 05:47:16 UTC, Andrei Alexandrescu
wrote:
Brian, should we add you? LMK. -- Andrei
indeed!
One week left!
On Tuesday, 13 October 2015 at 17:59:28 UTC, deadalnix wrote:
Hilter was very passionate too, are you saying he was right?
ICH BIN EIN POLYNOMIAL!
As this thread has run it course starting with the Hitler
comparison, and is therefor OT.
You have to explain to me, why your are a polynomial
On Tuesday, 13 October 2015 at 18:24:13 UTC, deadalnix wrote:
That's a reference to The Oatmeal :
http://theoatmeal.com/comics/atheism
thanks
This is the voting thread for inclusion of
std.experimental.testing into phobos.
PR: https://github.com/D-Programming-Language/phobos/pull/3207
Dub: http://code.dlang.org/packages/unit-threaded
Doc: See CyberShadow/DAutoTest for up-to-date documentation build
Formal Review Thread:
http://forum.dlang.org/post/jnihyetudelpkvrxl...@forum.dlang.org
Review of std.experimental.testing formal review
the two weeks of the formal review phase are over.
The review thread was very shallow. Dicebot again expressed this
disaffection with the assert function names
"should(BeTrue|BeFalse|...)" No agreement could be found.
Personally, I'm not sure
On Thursday, 24 September 2015 at 00:10:34 UTC, Martin Nowak
wrote:
Glad to announce D 2.068.2.
Congratulations
On Friday, 18 September 2015 at 11:35:45 UTC, John Colvin wrote:
Posting here instead of learn because I think it uncovers a
design flaw
void main(string[] args)
{
import std.file : dirEntries, SpanMode;
import std.stdio : writeln;
foreach(file; dirEntries(args[1], SpanMode.depth))
On Friday, 18 September 2015 at 12:42:26 UTC, John Colvin wrote:
Yes, but implicit in this being an OK solution for people is
that no-one ever reorganises the internals of DirIteratorImpl.
I guess One could use handle to deal with *all* the range
primitives as a defensive countermeasure.
On Friday, 18 September 2015 at 12:17:25 UTC, John Colvin wrote:
That's neat, didn't know about std.exception.handle
It is at least a year old. I created it because I had a range
that threw, and there was nothing to keep a range going or
reenter it.
Unfortunately, I think there are two
http://forum.dlang.org/post/stbdckpfsysjtppld...@forum.dlang.org
This post marks the start of the two week review process of
std.experimental.testing.
PR: https://github.com/D-Programming-Language/phobos/pull/3207
Dub: http://code.dlang.org/packages/unit-threaded
Doc: See CyberShadow/DAutoTest for up-to-date documentation build
Previous Thread:
On Wednesday, 9 September 2015 at 07:04:05 UTC, Per Nordlöw wrote:
Which direction should we choose?
quantities
Why not go really big. aka:
http://forum.dlang.org/post/vzcvwrbqpeamtnopm...@forum.dlang.org
On Tuesday, 8 September 2015 at 09:07:10 UTC, Edwin van Leeuwen
wrote:
Just to be clear. The PR is to add the needed ground work for
adding benchmark, or does it also add some benchmarks itself?
The PR adds benchmarks for some functions of std.string.
It does seem a bit of a shame not to
On Tuesday, 8 September 2015 at 08:42:59 UTC, Edwin van Leeuwen
wrote:
This does sound like a really good idea. Is the plan to turn
every unittest block into a benchmark (automatically), or did
you add specific benchmarks blocks?
you would add specific benchmark blocks, because the benchmarks
On Tuesday, 8 September 2015 at 12:24:19 UTC, tchaloupka wrote:
On Tuesday, 8 September 2015 at 09:20:08 UTC, Robert burner
Schadek wrote:
On Tuesday, 8 September 2015 at 09:07:10 UTC, Edwin van
Leeuwen wrote:
Just to be clear. The PR is to add the needed ground work for
adding benchmark, or
the sharedLog Logger (aka default logger) will only work after
its static this has run.
you could create a new Logger and use this one.
static this() {
auto tmpLog = new FileLogger("logfile.log");
tmpLog.log("Hello World");
}
Everybody is talking about benchmarks and making code faster, yet
phobos is still lacking any long term benchmark gathering and
monitoring solution.
PR https://github.com/D-Programming-Language/phobos/pull/2995
provides all that, and is done some time now. It will give us
pretty pictures we
On Wednesday, 2 September 2015 at 06:57:12 UTC, drug wrote:
Before 2.067 I used std.experimental.logger in form of a dub
package. Because it included in 2.067 I stop using the dub
package but now I get the error:
Error: safe function
my guess is that
InitiatingPTrack.toString is not @safe
Awesome job Daniel!
I will do the review management
Yes
On Friday, 3 July 2015 at 02:17:59 UTC, Timon Gehr wrote:
On 07/03/2015 04:17 AM, Timon Gehr wrote:
Bitwise are no math operations, these are CS operations
What does that even mean?
That there are no bitwise operations in math.
On Thursday, 2 July 2015 at 00:29:46 UTC, rsw0x wrote:
all bitwise ops except for shifting are fundamental math
operators just like addition and subtraction if you view an
integer as a bitstring(which is what it is...)
I must have missed something in my math classes.
Like the natural
On Thursday, 2 July 2015 at 20:24:55 UTC, tsbockman wrote:
I don't see why the closed-ness of the integers under an
operation should determine whether it makes the cut or not, but
if that's the standard:
I wanted to have an Integral type. And Math Integrals only have
the base operations
On Tuesday, 30 June 2015 at 20:24:38 UTC, tsbockman wrote:
4. Robert has suggested that a SafeInt type should disable
bitwise operations like ~, , |, ^, but I don't understand why.
The name SafeInt and the missing bitwise operations go in tandem.
SafeInt is a math type, +-/*% nothing more.
nice read, thank you
On Saturday, 13 June 2015 at 15:43:58 UTC, Andrei Alexandrescu
wrote:
I'd say we hold off on this until we finalize reference
counting. Right now std.logger requires GC. -- Andrei
for thread safety and performance we need to allocate strings.
what happened to RCstring?
std.(experimental.)logger has been in phobos for one release. The
idea was to mature stuff in experimental for one release and then
have a vote on inclusion into phobos as std.logger.
I would like to see this vote happen before 2.068.
Unfortunately, Dicebot is not longer the review manager.
On Wednesday, 10 June 2015 at 09:12:17 UTC, John Chapman wrote:
Logging
std.experimental.logger!?
On Monday, 8 June 2015 at 06:43:59 UTC, Jacob Carlborg wrote:
A completely new module should go through the review queue [1]
and no pull request should be created until it's passed the
review.
The part about the PR would be a first and quiet useless.
On Monday, 8 June 2015 at 10:33:12 UTC, Dmitry Olshansky wrote:
along with documentation (where's DDoc, Robert?).
http://burner.github.io/phobos/phobos-prerelease/std_experimental_safeint.html
Phobos is awesome, the libs of go, python and rust only have
better marketing.
As discussed on dconf, phobos needs to become big and blow the
rest out of the sky.
http://wiki.dlang.org/DIP80
lets get OT, please discuss
SafeInt!T is an integer wrapper struct with an explicit NaN value
build on top of core.checkedint.
Features:
* checks if assigned values can be actually stored
* for SafeInt!u(T) NaN is T.max
* for SafeInt!T NaN is T.min
* SafeInt!T.opBinary(+,-,%,*,/) return SafeInt!T
if value can not be
PR: https://github.com/D-Programming-Language/phobos/pull/3389
On Thursday, 4 June 2015 at 14:46:39 UTC, Dicebot wrote:
dcd
- new package, release 0.6.0
- only x86_64 for now (upstream bug)
- provides systemd service : `sudo systemctl enable
dcd.service` to start automatically upon system startup
this is totally awesome, thank you
I believe you're a aiming to low.
If you have a struct you could use traits and ctfe to generate
perfect sql statements. This would make it possible to a range of
struct Customers.
That would be awesome
On Thursday, 28 May 2015 at 04:45:52 UTC, Erik Smith wrote:
Shouldn't the statement be reusable?
Yes it should. I added this use case:
auto stmt = con.statement(insert into table values(?,?));
stmt.execute(a,1);
stmt.execute(b,2);
stmt.execute(c,3);
struct Table;
Table a, b, c;
On Friday, 8 May 2015 at 11:00:01 UTC, Chris wrote:
I'm sure there is room for improvement.
It looks like your reading some kind of comma seperated values
(csv).
have a look at std.csv of phobos
```
foreach(record;
file.byLine.joiner(\n).csvReader!(Tuple!(string, string,
int)))
{
On Sunday, 3 May 2015 at 23:32:28 UTC, Michel Fortin wrote:
This isn't a feature request (sorry?), but I just want to point
out that you should feel free to borrow code from
https://github.com/michelf/mfr-xml-d There's probably a lot
you can reuse in there.
nice, thank you
- CTS to disable parsing location (line,column)
std.xml has been considered not up to specs nearly 3 years now.
Time to build a successor. I currently plan the following featues
for it:
- SAX and DOM parser
- in-situ / slicing parsing when possible (forward range?)
- compile time switch (CTS) for lazy attribute parsing
- CTS for encoding
if(0X.std.string.indexOf(0x, CaseSensitive.no) == 0)
should work
awesome job
On Monday, 20 April 2015 at 14:29:33 UTC, Atila Neves wrote:
I saw links to PRs past with generated docs but have/had no
idea how to get a similar result. Besides the html make target,
what is it a person has to do exactly? I'm going to edit the
wiki
On Tuesday, 21 April 2015 at 13:18:59 UTC, Atila Neves wrote:
This part I'd figured out; it's the getting it online for
others to see (and the need to do this as part of the PR) I had
troubles with.
I did use github pages https://pages.github.com/
I will have a look at it (properly this weekend)
On Wednesday, 8 April 2015 at 09:58:31 UTC, Sönke Ludwig wrote:
That's what we have the review thread for. The library is now
in a state that everyone can easily try out. If it were a
Phobos PR, that would be much more difficult (or I'd have to
maintain two versions in parallel).
from
Congratulations
IMO this should be a PR for phobos so all comments to the code
can be collected in one location.
Where is the benchmark against std.json and rapidjson?
I have PR
https://github.com/D-Programming-Language/phobos/pull/2995 open
since October 2014.
it includes:
* extensible haskell like quickcheck
* benchmarking with names and record keeping to see progress
* offline tool to plot benchmark results with gnuplot
* most std.string functions already
On Monday, 30 March 2015 at 23:29:40 UTC, Jonathan wrote:
Thoughts?
Yes please, but as a part as phobos:
https://github.com/D-Programming-Language/phobos/pull/2995
101 - 200 of 417 matches
Mail list logo
