On 2015-01-19 04:17, Andrei Alexandrescu wrote:
Yah. The ones I found were paid. My point is ddoc was there and fit the
job perfectly well.
libsass [1] is a C implementation of Sass. Original implementation of
Sass is in Ruby.
This is a confusion - css minification is a separate topic alto
On 2015-01-19 03:31, Andrei Alexandrescu wrote:
So now minification and gzipping are the culprit? I don't quite understand.
There are plenty existing web frameworks that already have solved, what
it seems like, all the problems you're trying to solve now. You're just
shooting them down becau
On 2015-01-19 18:00, DaveG wrote:
The vertical menu expanded from the top works well with relatively few
items (in the case of bootstrap, eight). Personally, I don't think that
method works well with many items (we currently show 13, and up to 26
when expanded). It is particularly weird when the
On 2015-01-19 16:57, Andrei Alexandrescu wrote:
I think that would be great. Who wants to champion this project? Our
webmaster is okay with it and can arrange a domain such as new.dlang.org
to work the kinks out.
Takers?
I would like to but I have too many other projects going on right now.
On 2015-01-19 15:54, Dicebot wrote:
Framework doesn't really matter (though dog-fooding is desirable) - it
is a matter of maintainability. You may like RoR but how many people in
D community will be able to maintain such solution if you disappear? I
doubt many.
I said like 100 times now that vi
On 2015-01-19 13:00, "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?=
" wrote:
I would suggest you avoid frameworks since they go out of fashion fairly
quickly and makes maintenance dependent on individuals (with framework
knowledge). jQuery adds little value since browsers are fairly
standards-compliant
On 2015-01-19 16:47, Adam D. Ruppe wrote:
Yeah, the change itself is minor, but I'm hoping it might be indicative
more coming in the coming months; adding it to the test cases means we
might have significant stuff to test soon.
Then we can wait until there's actually anything useful added.
--
On 2015-01-21 03:59, Andrei Alexandrescu wrote:
Deployed. Let's thank Vladimir for this great work! -- Andrei
The icons need higher resolution for retina displays. Especially the
expand (plus) icons in the menu.
--
/Jacob Carlborg
On 2015-01-21 08:21, Jacob Carlborg wrote:
The icons need higher resolution for retina displays. Especially the
expand (plus) icons in the menu.
Using glyphs/text as icons, with a special font should be considered, i.e.:
* Font Awesome - http://fortawesome.github.io/Font-Awesome/
* Glyphicons
On 2015-01-21 10:28, Manu via Digitalmars-d wrote:
Super awesome!
Does LLDB have any support for D though?
No, not that I've heard of :(
--
/Jacob Carlborg
On 2015-01-21 22:38, Andrei Alexandrescu wrote:
Pushed. Looks better now? -- Andrei
Actually not so much. Is the site updated?
--
/Jacob Carlborg
On 2015-01-21 22:52, DaveG wrote:
You're not alone gents. I like some parts and content pages aren't too
bad, but the homepage is completely impractical. It feels like I'm
emulating a giant phone. The problem with "mobile first" design is the
desktop often gets left behind. This may not be a pro
On 2015-01-23 01:24, Andrei Alexandrescu wrote:
I think it's important that we enable Calypso
(https://github.com/Syniurge/Calypso) and related tooling that
interfaces D with other languages, notably C++.
I could always use some help with DStep [1]. For those who doesn't know,
it's an automate
On 2015-01-23 11:31, aldanor wrote:
Hi all, I've started redesigning dlang.org AGAIN (yea, I know...). The
front page is mostly done aside from a several responsiveness and
platform quirks, I will have the full landing page + a random sample
page from the docs this weekend. On the technical side,
On 2015-01-23 11:31, aldanor wrote:
Top-level-link: CHANGELOG
... is stale and rarely / randomly updated. This makes it look like
there is no development on the backend/phobos/runtime going on
whatsoever. There either needs to be an automated aggregator for github
pull requests (in which case t
On 2015-01-23 11:52, Walter Bright wrote:
Yes, it's tied to clang++. It may not even work on all the platforms we
support. But that's no matter for now.
At least Clang supports all platforms we support.
--
/Jacob Carlborg
On 2015-01-23 17:02, Andrei Alexandrescu wrote:
We should make the life of plugin writers easy. They do get to decide
what other prerequisites their tools have.
Are you suggesting to have a general plugin architecture in DMD? That
would be very cool, especially if they can be installed as Dub
On 2015-01-23 19:43, Andrei Alexandrescu wrote:
On that front, a coworker gave me a simple idea for integration.
1. All C++ non-polymorphic types thrown cannot be caught in D
2. We (or Calypso) define D class counterparts for polymorphic types
thrown from C++, notably std::exception and subtyp
On 2015-01-24 03:43, anonymous wrote:
Inspired by the recent developments, and Sebastiaan Koppe's version [1]
specifically, I gave it a go, too:
http://ag0aep6g-dlang.rhcloud.com/
The search "area" doesn't look good, especially the drop down. For
example it's not possible to style the arrow i
On 2015-01-24 18:45, Robert burner Schadek wrote:
I will fix the bug this weekend and rebase to upstream/master. The alias
doc has seen some updates this week (please check the rebuild gh-pages,
links are in the PR description)
Is the generated documentation for package module available somewhe
On 2015-01-25 01:50, H. S. Teoh via Digitalmars-d wrote:
Since we're in the middle of many website revamps, here's a good time to
consider this very important issue, as illustrated by somebody asking on
the d-learn forum why dlang.org talks about AA.byKeyValue but the
current release doesn't have
On 2015-01-26 01:37, Walter Bright wrote:
I'm obviously terrible at communicating. Let me try again. Assume that I
wrote Calypso, and I was explaining it to you:
-
Given the C++ header file foo.h:
void bar(unsigned *);
and the C++ source file foo.
On 2015-01-26 08:35, H. S. Teoh via Digitalmars-d wrote:
I think we should just import jquery into the dlang.org repo. External
dependencies always end up in these kinds of ugly situations.
The advantage of using a CDN is that browser will most likely already
have loaded, in this case jQuery,
On 2014-04-16 19:52, Adam D. Ruppe wrote:
What I want is a __trait that scans for all call expressions in a
particular function and returns all those functions.
Then, we can check them for UDAs using the regular way and start to
implement library defined things like @safe, @nogc, etc. (safe and
On 2014-04-17 15:08, Orvid King via Digitalmars-d wrote:
Lastly, I'll add support for stack allocated
classes, however that will likely have to be disabled until DMD gets
full escape analysis. As a final note, this will be the 3rd GC I've
written, although it will be the most complex by far. The
On Friday, 18 April 2014 at 15:49:59 UTC, Andrei Alexandrescu
wrote:
We can (and probably should) integrate server-side scripting as
well. http://dlang.org/bugstats uses PHP. Ideally we'd migrate
the entire website to vibe.d.
Yes please. Ddoc might be better than plain HTML but most other
f
On Friday, 18 April 2014 at 16:40:32 UTC, Aleksandar Ruzicic
wrote:
I must respectfully disagree about retaining left justification.
I have 27'' monitor with resolution of 2560x1440 and
left-aligned websites are really hard to read!
Agree. I think we should use Bootstrap. Then we can also ge
On 2014-04-18 18:17, Brad Anderson wrote:
Problems like how toUpperInPlace would still allocate (with
gusto) could much more easily be recognized and fixed with @nogc available.
toUpperInPlace should be removed. It cannot work reliable in place.
--
/Jacob Carlborg
On 2014-04-18 22:25, Walter Bright wrote:
dmd could do a better job of escape analysis, and do this automatically.
That would be really nice. Is this long hanging fruit or does it require
a lot of work?
--
/Jacob Carlborg
On 2014-04-19 10:54, Aleksandar Ruzicic wrote:
Bootstrap is great but I wouldn't use it for this project. As it might
be difficult to work with when you don't want that "bootstrap style
look". OTOH Zurb's Foundation framework is all about structure and it
leaves styling up to you which is great.
On 2014-04-19 12:21, bearophile wrote:
Better to move it in std.ascii instead of removing it.
The current implementation works with more characters than ASCII.
--
/Jacob Carlborg
On 2014-04-17 16:59, Steven Schveighoffer wrote:
I don't think this is a viable mechanism to check pointers. It's too slow.
Couldn't a single bit be used to indicate if it's a GC pointer or not?
--
/Jacob Carlborg
On 2014-04-19 15:40, monarch_dodra wrote:
Nonsense. It still works 99% of the time (I think only a subset of 100
letters in all of Unicode are affect, and even then, another 100 of them
*shrink* on toUpper). It is really useful. It avoids *needles*
allocations. Removing it would be more harmful
On 2014-04-19 23:06, Nick Sabalausky wrote:
God no. I like forum.dlang.org and all, but scaling the font size when
the window resizes is horrible UX. Example: If I shrink the browser
window, for *whatever* reason, I expect not to have an over-zealous CSS
decide "Oh! He must want the text to beco
On 2014-04-19 13:09, Aleksandar Ruzicic wrote:
I have experience with ElasticSearch but I'm open to all suggestions, if
Solr is better, then we'll use Solr.
But this is something Walter must approve first, as it would mean
ditching Google search in favor of our own search service.
They're quir
On Sunday, 20 April 2014 at 14:38:47 UTC, Frustrated wrote:
How bout this!
Why not allow one to define their own attributes from a
generalized subset and then define a few standard ones like
@nogc.
Sounds like you want AST macros. Have a look at this
http://wiki.dlang.org/DIP50#Declaration
On 21/04/14 10:49, Lars T. Kyllingstad wrote:
Ok, so "any number" was poorly phrased. What I meant was "a large
number", because in my experience, modules tend to be quite large.
Specifically, they are rarely limited to containing just a single
class. They often contain multiple classes, along
On 21/04/14 23:33, Dicebot wrote:
I think it is very important to dogfood here and add any currently
missing dependencies as dub packages instead.
Unless we can use libsass, I would say it's not very productive to
implement a new Sass compiler, just to avoid a dependency.
--
/Jacob Carlborg
On 21/04/14 23:23, Andrei Alexandrescu wrote:
I confess getting a bit uncomfortable about adding new dependencies at
this point. We depend on dpl-docs already, and the tool was difficult to
install and broke from one dmd release to the next. Sönke was nice and
proactive about it, but he's an act
On 21/04/14 19:49, Frustrated wrote:
Not quite. AST macros simply transform code. Attributes attach meta data
to code. While I'm sure there is some overlap they are not the same.
Unless AST macros have the ability to arbitrary add additional
contextual information to meta code then they can't e
On 22/04/14 01:02, Walter Bright wrote:
The thing is, with iOS ARC, it cannot be statically guaranteed to be
memory safe. This makes it simply not acceptable for D in the general
case. It "works" with iOS because iOS allows all kinds of (unsafe) ways
to escape it, and it must offer those ways be
On 2014-04-22 11:20, Yuriy wrote:
Hello, is there a way of getting CT info of a class' children?
Not in a pretty way but I think this should work:
* Implement a custom RTInfo in object.d in druntime. This template will
be instantiated with all user defined types
* For each type that is a cl
On 2014-04-22 09:56, "Ola Fosheim Grøstad"
" wrote:
I never use css macros-tools, regular template libraries are usually
better (e.g. jinja2 allows me to execute python expressions if needed).
With current browsers the CSS is getting much more streamlined too and
the worst browser bugs require
On 2014-04-22 14:21, w0rp wrote:
I like your design. Go forth and make it happen.
On line length, the optimal line length is somewhere between 70 and 110
characters from what I have read. I found one study here which didn't
turn up a great observable difference in reading speed or comprehension
On 2014-04-22 18:38, Andrei Alexandrescu wrote:
I'm clearly outta my depth here, basing myself off of giving
http://sass-lang.com/guide a couple minutes. From what I can tell here's
how ddoc matches up sass features:
Pre-processing: yes
Variables: yes
Nesting: no
Partials, Import: somewhat (by
On 23/04/14 06:33, Walter Bright wrote:
I repeatedly said that it is not memory safe because you must employ
escapes from it to get performance.
Apparently you need that for the GC as well, that's why this thread was
started to begin with.
--
/Jacob Carlborg
On 22/04/14 20:48, Steven Schveighoffer wrote:
I mean not like I can't because I don't want to or don't have time, but
can't as in I lack the skill set :) It's interesting to debate, and I
get the concepts, but I am not a CPU/cache guy, and these things are
really important to get right for perf
On 22/04/14 22:50, Yuriy wrote:
Any way to do it without patching druntime?
Not that I know of.
--
/Jacob Carlborg
On 22/04/14 20:06, Brian Schott wrote:
We have "alias a = b;" and "alias b a;", so there's precedent for having
two ways of doing exactly the same thing.
I believe that for aliasing function pointers only the latter syntax works.
--
/Jacob Carlborg
On 23/04/14 00:57, Nick Sabalausky wrote:
Apparently they can't even manage make basic links work properly:
http://getbootstrap.com/examples/starter-template/
How anyone can manage to fuck up ... is beyond me.
What's fucked up with the links?
--
/Jacob Carlborg
On 23/04/14 10:31, Walter Bright wrote:
Manu, you obviously believe in ARC. I've made an attempt to do ARC,
detailed in the other thread here. I failed.
http://forum.dlang.org/thread/l34lei$255v$1...@digitalmars.com
That conversation started out from the D/Objective-C conversations. To
have A
On 23/04/14 13:39, Joakim wrote:
Alright, finally hacked dmd to produce something like packed TLS for
ELF. I just ran the druntime unit tests on Android/x86 and all 38
modules passed, :) even after changing the number of TLS variables a
couple times, which was causing segfaults with the native
On 2014-04-23 17:57, Steven Schveighoffer wrote:
Sure, but there are things I CAN do with my limited time, that I do have
the expertise for. I've already been schooled by the likes of you and
Michel Fortin on my knowledge of ref counting implementation.
That's completely different. I've felt t
On 23/04/14 19:12, Walter Bright wrote:
Too many double negatives for me to be sure what you're saying. But it
is clear to me that with Michel's experience with ARC in iOS combined
with Manu's enthusiasm for it suggests that they are the right team to
come up with a workable proposal, where mine
On 24/04/14 00:29, Martin Nowak wrote:
Looks fairly interesting, because it partly solves the issue to allow
custom rtinfo.
I don't like this solution for custom RTInfo. It requires you to change
your type. I would rather modify the compiler to do something like this:
* Add a UDA to druntim
On 23/04/14 08:39, Walter Bright wrote:
I made a build of dmd with a collector in it. It destroyed the speed.
Took it out.
Isn't that bad advertisement for the GC in D? Or has it something to do
with DMD not being designed with a GC in mind?
--
/Jacob Carlborg
On 24/04/14 00:12, Nick Sabalausky wrote:
SCSS has always been more interesting to me than SASS, but yea, this
seems to pretty much be an independently-developed equivalent to SCSS,
which is pretty cool.
Technically, Sass is the name of the language. It provides two syntaxes,
SASS and SCSS. S
On 24/04/14 00:08, Nick Sabalausky wrote:
They don't work.
But...maybe they're only intended to be single-page-only examples? (Now
that I think about it...)
Yes. Bootstrap won't touch your links with JavaScript, unless you tell
it to.
If so, then I must have misunderstood the examples. Th
On 2014-04-24 16:19, Adam D. Ruppe wrote:
Hmm, looking at the sass webpage, I think I could do some of the
features but prolly not all and with a different syntax. So it wouldn't
work for a full scss compiler.
Sass really has some advanced features. It's possible to create a
function in Ruby
On 24/04/14 23:49, bearophile wrote:
Yes, sorry, I know this could cause some troubles, but if you think hard
about the situation, you will see that this is currently the best (or
less bad) solution. It was recently discussed in D.learn, but I can't
find the thread. So let's not discuss it again
On Friday, 25 April 2014 at 15:29:38 UTC, Steven Schveighoffer
wrote:
Well, @nogc is not released yet. Please tell me we don't have
to avoid breaking code based on git HEAD...
We've already done that before, with UDA's. So, you never know.
--
/Jacob Carlborg
On 2014-04-25 16:28, bearophile wrote:
This problem was underlined during this thread far before the merging of
the @nogc implementation. Why have Walter & Andrei ignored the problem?
What's the point of creating a DIP if you ignore the problems found in
its discussion? What's the point of 338 c
On 2014-04-26 11:31, Walter Bright wrote:
http://wiki.dlang.org/DIP61
Best practices in C++ code increasingly means putting functions and
declarations in namespaces. Currently, there is no support in D to call
C++ functions in namespaces. The primary issue is that the name mangling
doesn't match
On Saturday, 26 April 2014 at 09:31:48 UTC, Walter Bright wrote:
http://wiki.dlang.org/DIP61
Best practices in C++ code increasingly means putting functions
and declarations in namespaces. Currently, there is no support
in D to call C++ functions in namespaces. The primary issue is
that the n
On 2014-04-26 16:43, Daniel Murphy wrote:
At least these days it only happens when Walter and Andrei agree instead
of just Walter merging whatever he feels like.
Yeah, but it's still a problem when the rest of the community disagrees.
--
/Jacob Carlborg
On 27/04/14 21:39, Walter Bright wrote:
std.datetime is a giant kitchen sink. This is not the best way to
organize things. Using smaller modules under packages is a much better way.
It's taken an amazingly long time for the core developers to realize
this. I'm glad it's happened tough :)
--
On 28/04/14 10:14, Andrej Mitrovic via Digitalmars-d wrote:
Really? I've seen everyone complain about it from day 1.
When I started to complain about having too big modules nobody agreed.
--
/Jacob Carlborg
On 28/04/14 08:49, Walter Bright wrote:
We've known it for a long time, but nobody has done anything about it.
For example, the new package.d feature was specifically designed so that
long modules can be broken up without breaking user code. Nobody has yet
modified any Phobos code to actually d
On 2014-04-29 17:27, Adam D. Ruppe wrote:
I recently started a Ruby on Rails job and using it makes me really,
really miss the high productivity and ease of use D offers.
I'm curious to why you think D is more productive and easier to use.
--
/Jacob Carlborg
On 30/04/14 00:09, Adam D. Ruppe wrote:
A lot of things, mostly focusing around having the compiler to help
refactor with confidence (the importance of this really can't be
understated) and having libraries that fit better.
I think one of the great things about Rails and Ruby is all the
libra
On 2014-04-30 18:55, Andrei Alexandrescu wrote:
Walter and I also discussed "static unittest" a while ago - yes, another
use of static :o).
A static unittest would be evaluated only during compilation, and would
prove things that fall in the realm of static checking but are not
verifiable with t
On 2014-04-30 15:38, Adam D. Ruppe wrote:
Of course, I doubt the gap will ever be closed, since Ruby's awfulness
isn't dependent on my experience level. It's not like it will ever get
static typing even if I used it all the time. It won't get faster.
ActiveRecord won't get sane.
Ruby has gotte
On 2014-04-30 11:43, Dicebot wrote:
This is common complaint I still fail to understand. I have never ever
wanted to run a single unit test, why would one need it? If running all
module tests at once creates problems than either module is too big or
unit tests are not really unit tests.
Why wo
On 2014-04-30 17:04, Adam D. Ruppe wrote:
I like implementing things myself :P
That's the question I dread most at meetings now: "is there a gem for
this?" idk, in the time it takes to search for and evaluate third party
code, I could have just written it myself. Especially since libraries
almo
On 2014-04-30 17:43, Andrei Alexandrescu wrote:
Hello,
A coworker mentioned the idea that unittests could be run in parallel
(using e.g. a thread pool). I've rigged things to run in parallel
unittests across modules, and that works well. However, this is too
coarse-grained - it would be great i
On 2014-04-30 19:30, Dicebot wrote:
I believe only missing step right now is propagation of UDA's to RTInfo
when demanded. Everything else can be done as Phobos solution.
I don't see why this is necessary for this case.
--
/Jacob Carlborg
On 2014-04-30 22:11, Russel Winder via Digitalmars-d wrote:
This cannot be a good idea. If the block says unittest then it contains
unit tests, not integration tests or system tests, just unit tests.
Then we need to come up with a separate framework for doing all other
kinds of tests.
--
/J
On 2014-04-30 22:38, Adam D. Ruppe wrote:
Yeah, foreign keys are really an absolute must. So are uniqueness
constraints. Rails can kinda do these, but in its own reinvented ways
that don't actually hit the DB (at least not without add on gems)
Rails unique constraints do hit the DB, but they c
On 2014-04-30 22:36, Nick Sabalausky wrote:
Aren't you talking about databases? Single-threading won't save you from
races there unless the DBMS itself is single-threaded (which would be a
pretty undesirable DBMS).
Are you referring to if one process executes line 1 while another
executes lin
On 2014-04-30 23:25, Jonathan M Davis via Digitalmars-d wrote:
Sure, that helps, but it's trivial to write a unittest block which
depends on a previous unittest block
There for the tests should be run in random order.
--
/Jacob Carlborg
On 2014-04-30 23:35, Andrei Alexandrescu wrote:
Agreed. I think we should look into parallelizing all unittests. -- Andrei
I recommend running the tests in random order as well.
--
/Jacob Carlborg
On 2014-04-30 21:12, bearophile wrote:
Are UDAs enough?
@uname("foo") unittest {}
What I'd like is to tie one or more unittests to other entities, like
all the unittests of a specific function.
Something similar is done in RSpec. A BDD framework in Ruby. In D it
might look like this:
@des
On 2014-05-01 11:37, Dicebot wrote:
You only need to make sure all modules are transitively imported from
initial one.
The solution for that would be RMInfo [1], like RTInfo but for modules
instead of types.
[1] https://github.com/D-Programming-Language/dmd/pull/2271
--
/Jacob Carlborg
On 2014-05-01 09:10, Dicebot wrote:
It is not strictly necessary but you can't reliably get all unit test
blocks during compile-time (must be transitively imported) and current
run-time reflection for tests is missing any data but actual function
pointers. I am personally perfectly satisfied wit
On 2014-04-30 22:41, Andrei Alexandrescu wrote:
Yah I think that's possible but I'd like the name to be part of the
function name as well e.g. unittest__%s.
Why is that necessary? To have the correct symbol name when debugging?
I'm using something quite similar to RSpec from the Ruby world:
On 2014-05-01 14:00, Johannes Pfau wrote:
But on a quick look I don't understand how this (or DRT #775) completely
solves the issue.
Now you don't have to import the modules anymore, which is a step
forward, but let's say I want to used this to find all SubClasses of a
class.
Now I can inspect
On 2014-05-01 15:54, "Marc Schütz" " wrote:
You can also use the built-in `includes()`, which does a LEFT OUTER JOIN:
Post.includes(:comments).where(comments: {title: "bar"})
(It also eager-loads the comments, but this is usually desired anyway,
because an OUTER JOIN doesn't make sense if
On 2014-05-01 19:12, Steven Schveighoffer wrote:
But not a great way to debug it.
If your test failure depends on ordering, then the next run will be
random too.
Proposal runtime parameter for pre-main consumption:
./myprog --rndunit[=seed]
To run unit tests randomly. Prints out as first ord
On 2014-05-01 19:56, "Marc Schütz" " wrote:
Exactly. I just feel that client-side validation is unnecessary
duplication in most cases. But sure, it can be used where it makes sense.
There's a gem [1] for that. Although it seems that one is not maintained
anymore.
[1] https://github.com/Dock
On 2014-05-01 17:15, Andrei Alexandrescu wrote:
That's all nice, but I feel we're going gung ho with overengineering
already. If we give unittests names and then offer people a button
"parallelize unittests" to push (don't even specify the number of
threads! let the system figure it out dependin
On 02/05/14 02:22, H. S. Teoh via Digitalmars-d wrote:
I was reading this article of Walter's:
http://www.drdobbs.com/cpp/the-x-macro/228700289
Which is a neat trick that I wish I'd known back when I was writing
C/C++. But the thought crossed my mind: what's the D equivalent of the X
ma
On 01/05/14 21:55, "Marc Schütz" " wrote:
You're probably right. I thought that changed in a recent release, but
can't find it anymore.
I don't know. I wouldn't trust it. It's the behavior in Rails 3. I
haven't used Rails 4 yet.
--
/Jacob Carlborg
On 2014-05-02 17:38, "Marc Schütz" " wrote:
But my main point was actually this:
Don't disallow destructors on classes just because they are classes, but
disallow them when they are not guaranteed to be called (or calling them
is troublesome because of multi-threading), i.e. GC.
Tango for D1 a
On 2014-05-03 14:28, monnoroch wrote:
That leaves only to determine, what objects are scoped. Well, that is
obviously stack-allocated structs, gc-allocated scope classes and
gc-allocated structs in scope classes.
Will the destructor of GC allocated scope classes be called when its
surrounding
On 2014-05-03 21:52, Atila Neves wrote:
For me it's the output. I don't want to see the output of other
tests when I'm debugging a failure.
That's a good point.
--
/Jacob Carlborg
On 2014-05-03 21:51, Atila Neves wrote:
This is why I started to learn Cucumber.
Cucumber is for acceptance tests. There are also functional and
integration tests.
--
/Jacob Carlborg
On 2014-05-02 19:25, brad clawsie wrote:
this has been the fundamental issue for me. its not just missing libs,
its libs that are surfaced via a C-binding, which in my limited
I've had problems with ImageMagick, basically every time. But that's the
only one I can think of, at least for now.
On 04/05/14 20:26, Jonas Drewsen wrote:
Just had a quick look at the source code.
If this is to be something like the official gfx library wouldn't it
make sense to follow the phobos coding style?
For example "struct Size" instead of "struct SIZE"
To me, most code there looks like bindings.
-
On 04/05/14 23:20, Daniele M. wrote:
You are right, devs would eventually abuse everything possible, although
it would make it for sure more visible: you cannot advertize an un-@safe
library as @safe, although I agree that a lot depends from devs/users
culture.
In D, you can at least staticall
On 05/05/14 00:55, H. S. Teoh via Digitalmars-d wrote:
I'm sorry, but this is patently false. I am neither in the inner circle,
nor do I represent any corporation, yet I've had many changes pulled
into Phobos (including brand new code).
I think he's referring to language changes. Things that w
401 - 500 of 2325 matches
Mail list logo
