"Deja Augustine" <Deja_member@pathlink.com> wrote in message news:cfum32$21ab$1@digitaldaemon.com...
> In article <cftrke$1fg1$1@digitaldaemon.com>, Walter says...
> >
> >
> >"Helmut Leitner" <leitner@hls.via.at> wrote in message news:412200EF.42A6A05B@hls.via.at...
> >> I think it would be better to spread the load among different persons.
> >>
> >> A professional author (like Matthew for example) can do it much easier and without negative effects on language development and support.
> >>
> >> The problem is perhaps that the language must be stable, otherwise this "language bible" is quickly outdated.
> >>
> >> There should also be program examples for all important application areas to let D really shine.
> >
> >For me also, writing articles and books always reminds me of writing term papers back in college. Not my favorite task <g>. Matthew and I have written some articles about D and they've been published in CUJ and DDJ. I have another one pending with DDJ.
> >
> >But there's nothing stopping anyone here from writing articles about D. I know I'm a little weary of reading articles about C++, so much ground has been repeatedly covered by articles that newer articles seem to be mostly about esoterica, not much of interest to mainstream C++ coding. But the article space for D is vast, unexplored territory, and fertile ground for articles. And CUJ and DDJ actually pay money for articles! Their editorial staffs have indicated to me they are very receptive to articles about D.
> >
> >Many of you are expert D programmers and are experts at particular kinds of D programming applications. Writing articles about your products would be straightforward, such as articles about unicode programming, gui programming, threading, templates, etc. How about it?
> >
> >
>
>
> Out of curiosity, how does one go about sumitting articles to CUJ or DDJ?

You'll need a proposal, which should be a couple of paragraphs saying what's interesting and/or unique about your article. It should also have an estimate of length, and # of code snapshots, etc.

Since I'm wildly overexposed in both those mags, I have some experience with the process. If you want to fire a proposal across my bows before you submit it, that's perfectly fine with me. :)


-- 
Matthew Wilson

Author: "Imperfect C++", Addison-Wesley, 2004
    (http://www.imperfectcplusplus.com)
Contributing editor, C/C++ Users Journal
    (http://www.synesis.com.au/articles.html#columns)
Director, Synesis Software
    (www.synesis.com.au)
STLSoft moderator
    (http://www.stlsoft.org)

"Youth ages, Immaturity is outgrown, Ignorance can be educated, drunkeness sobered. But stupid lasts forever", Aristophenes

-----------------------------------------------------

"John Reimer" <brk_6502@NOSP_AM.yahoo.com> wrote in message news:cfuqat$22tq$1@digitaldaemon.com...
> kinghajj wrote:
>
> >>"Helmut Leitner" <leitner@hls.via.at> wrote in message news:412200EF.42A6A05B@hls.via.at...
> >
> >
> >>>A professional author (like Matthew for example) ...
> >
> >
> > Really? What books have you written, Matthew?
> >
> >
>
> AHHH! You had to ask him that question!
>
> <g>
>
> Just ribbing you, Matthew  ;-)

Consider me ribbed. :)

In article <cfu04n$1hq7$1@digitaldaemon.com>, "antiAlias" <fu@bar.com> wrote:

> "Walter" <newshound@digitalmars.com> wrote in message news:cftrke$1fg1$1@digitaldaemon.com...
> > Many of you are expert D programmers and are experts at particular kinds
> of
> > D programming applications. Writing articles about your products would be straightforward, such as articles about unicode programming, gui programming, threading, templates, etc. How about it?
> 
> How about one regarding the efficiency benefits of array-slicing? I might be able to cobble something together based on results from mango.http.server & mango.servlet (once 'primed', they make zero memory-allocations ~ the GC simply never runs).

I'm a little confused about array slicing still.   Does it make a copy of the data?  Or is it just a pointer to the innards of another array and a length?

If so, I can see how this would be a huge performance advantage.  I once wrote a parser that would read the file into memory, and make little copies of the data it needed from the database all over.  Really silly.

Then I re-implemented it with "slicing" basically. I destroyed the byte prior to the data with the length of the data and stored a pointer to it in my index.  Basically making a bunch of pascal strings.  The speed increase was outrageous.

Sha Chancellor schrieb:

> I'm a little confused about array slicing still.   Does it make a copy of the data?  Or is it just a pointer to the innards of another array and a length?

As opposed to Python, slicing never makes a copy of the data, it just creates another pointer. But be aware that concatenation always copies.

-eye

"Sha Chancellor" <schancel@pacific.net> wrote in message news:schancel-484B81.09180718082004@digitalmars.com...
> I'm a little confused about array slicing still.   Does it make a copy of the data?

No.

>  Or is it just a pointer to the innards of another array
> and a length?

Yes. It explicitly does not copy.

> If so, I can see how this would be a huge performance advantage.  I once wrote a parser that would read the file into memory, and make little copies of the data it needed from the database all over.  Really silly.

Yup.

> Then I re-implemented it with "slicing" basically. I destroyed the byte prior to the data with the length of the data and stored a pointer to it in my index.  Basically making a bunch of pascal strings.  The speed increase was outrageous.

Yup <g>. One neato thing about gc is it makes slicing practical. So, while gc can sometimes be slower, your app can overall be sped up quite a bit. This issue is poorly understood, and so would make a great article.

"Ilya Minkov" <minkov@cs.tum.edu> wrote in message news:cg0dvd$ve3$1@digitaldaemon.com...
> Sha Chancellor schrieb:
>
> > I'm a little confused about array slicing still.   Does it make a copy of the data?  Or is it just a pointer to the innards of another array and a length?
>
> As opposed to Python, slicing never makes a copy of the data, it just creates another pointer. But be aware that concatenation always copies.

That's right.

"D Programming Language in yo Mo fo face! Bitch!" or something.

It isn't funny but to me it is and sorry to anyone it may or may not have offended.


kinghajj wrote:
> In article <cfr625$2sul$1@digitaldaemon.com>, Chris S. says...
> 
>>Better title:
>>
>>"The D Programming Language... seriously."
>>
> 
> No, no. no: "The D Programming Language ... Don't Laugh! Check it out!".
> 
>