www.digitalmars.com         C & C++   DMDScript  

D - submissions thedjournal.com

reply "anderson" <anderson firestar.com.au> writes:
I've updated a few thing and wasn't going to send until I'd put a bit more
in. I haven't done that for a while so here it is. I've added a note about
some of D's specail cases, which may change in D later on.
Jun 20 2002
parent reply "anderson" <anderson firestar.com.au> writes:
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Woops I just did a "complier Walter", this was meant to go to =
submissions thedjournal.com. One of those one in a lifetime mistake kind =
of things.=20
Jun 20 2002
parent reply "Matthew Wilson" <matthew thedjournal.com> writes:
No worries, although "compiler walter*" is not a perjorative term, nor does
it indicate that someone has gaffed. Indeed, it is actually a term of
respect and endearment, to be applied to one whose knowledge is vast and
friendly.

Matthew

*compiler walter is a registered trademark of wilson megalomania
enterprises, incorporated

"anderson" <anderson firestar.com.au> wrote in message
news:aeu0pl$bbj$1 digitaldaemon.com...
Woops I just did a "complier Walter", this was meant to go to
submissions thedjournal.com. One of those one in a lifetime mistake kind of
things.
Jun 20 2002
parent reply "OddesE" <OddesE_XYZ hotmail.com> writes:
I have been a bit busy lately, and when I
reloaded the newsgroup, just to see that
there were over 700(!) unread messages, I
must say I was a bit overwhelmed. I got it
down to 400 by now, so I am sorry if I am
saying things that are already mentioned in
other posts, I probably haven't read them
yet...

I read the posts about the D journal up to
this point, and I really like the idea!
I would like to volunteer as an author. I
already have an Opinion piece in mind,
about error handling, and I would like to
write about D compared to Delphi too, because
I have some experience with Delphi.

My profile if you are interested:

Name:         Stijn de Witt
Birthdate:    19 december 1976
Country:      Nederland, Europe (the Netherlands)
Language:     Dutch
English:      Good, but still need to be checked
              by someone native in the language.
Education:    Just graduated Cum Laude in Computer
              Sciences in Hogeschool level, which
              compares to (just above) bachelor in
              the American system.
Experience:   I have been programming on and off
              for about 12 years, but only serious
              for about half of that.

Also I have some suggestions about the notes
in this thread:


- High Cohesion and Low Coupling:

I like the explanation of Coupling, but I
don't like the explanation of Cohesion.
Cohesion is not something that takes place
between different components, as the example
suggests, but inside one single component.
The tyre should have high cohesion with itself!


- Speed Optimisation with For Loops

I like this piece! It is a mistake often made
by newbies. But why not point out that instead
of a temporary variable Size, walking backward
might be used, as is explained in a tip earlier?
Like this:

for (int n=getSizeof(X)-1; n>=0; n--)
{
   ...
}

Also, the last line should read
That way your not calling the fucntion getSizeof(X) n times.


- Speed Optimisation for linear searches

I love this piece, it really learned me something!


Just one more little nag, compiler is not spelled complier...

Walter's stuff is not new ofcourse, but still probably
deserves a place in the magazine.


Well those were my 2 cents...

--
Stijn
OddesE_XYZ hotmail.com
http://OddesE.cjb.net
_________________________________________________
Remove _XYZ from my address when replying by mail
Jun 24 2002
next sibling parent reply "Matthew Wilson" <matthew thedjournal.com> writes:
Stijn

Excellent stuff! Thanks very much for this. I definitely want to hear from
you regarding the article ideas. For guidance, please check out
http://thedjournal.com/papers.html

And to everyone who has contributed so far, thanks for that. Your
contributions have not got lost! I have to apologise, as the last two weeks
have been a bit of a nightmare, and this and the next will be also, but
after that I should be getting back to the editing stuff, and will be in
touch.

And to everyone who has not contributed, please do so. The level of interest
we have so far makes me think this is going to be very popular, so something
to stick on the resume as well as knowing you're contributing to D common
good ;)

Matthew

"OddesE" <OddesE_XYZ hotmail.com> wrote in message
news:af7hjs$1cil$1 digitaldaemon.com...
 I have been a bit busy lately, and when I
 reloaded the newsgroup, just to see that
 there were over 700(!) unread messages, I
 must say I was a bit overwhelmed. I got it
 down to 400 by now, so I am sorry if I am
 saying things that are already mentioned in
 other posts, I probably haven't read them
 yet...

 I read the posts about the D journal up to
 this point, and I really like the idea!
 I would like to volunteer as an author. I
 already have an Opinion piece in mind,
 about error handling, and I would like to
 write about D compared to Delphi too, because
 I have some experience with Delphi.

 My profile if you are interested:

 Name:         Stijn de Witt
 Birthdate:    19 december 1976
 Country:      Nederland, Europe (the Netherlands)
 Language:     Dutch
 English:      Good, but still need to be checked
               by someone native in the language.
 Education:    Just graduated Cum Laude in Computer
               Sciences in Hogeschool level, which
               compares to (just above) bachelor in
               the American system.
 Experience:   I have been programming on and off
               for about 12 years, but only serious
               for about half of that.

 Also I have some suggestions about the notes
 in this thread:


 - High Cohesion and Low Coupling:

 I like the explanation of Coupling, but I
 don't like the explanation of Cohesion.
 Cohesion is not something that takes place
 between different components, as the example
 suggests, but inside one single component.
 The tyre should have high cohesion with itself!


 - Speed Optimisation with For Loops

 I like this piece! It is a mistake often made
 by newbies. But why not point out that instead
 of a temporary variable Size, walking backward
 might be used, as is explained in a tip earlier?
 Like this:

 for (int n=getSizeof(X)-1; n>=0; n--)
 {
    ...
 }

 Also, the last line should read
 That way your not calling the fucntion getSizeof(X) n times.


 - Speed Optimisation for linear searches

 I love this piece, it really learned me something!


 Just one more little nag, compiler is not spelled complier...

 Walter's stuff is not new ofcourse, but still probably
 deserves a place in the magazine.


 Well those were my 2 cents...

 --
 Stijn
 OddesE_XYZ hotmail.com
 http://OddesE.cjb.net
 _________________________________________________
 Remove _XYZ from my address when replying by mail

Jun 24 2002
parent reply "OddesE" <OddesE_XYZ hotmail.com> writes:
"Matthew Wilson" <matthew thedjournal.com> wrote in message
news:af88ii$2ptn$1 digitaldaemon.com...
 Stijn

 Excellent stuff! Thanks very much for this. I definitely want to hear from
 you regarding the article ideas. For guidance, please check out
 http://thedjournal.com/papers.html

 And to everyone who has contributed so far, thanks for that. Your
 contributions have not got lost! I have to apologise, as the last two

 have been a bit of a nightmare, and this and the next will be also, but
 after that I should be getting back to the editing stuff, and will be in
 touch.

 And to everyone who has not contributed, please do so. The level of

 we have so far makes me think this is going to be very popular, so

 to stick on the resume as well as knowing you're contributing to D common
 good ;)

 Matthew

Matthew, The idea for the opinion article is an article about error handling. Where to handle what kind of errors, ways to structure your code, what kind of errors should and should not be handled, error codes versus exceptions and design by contract. I also want to talk a bit about usefull error messages and preventing and detecting user errors... The idea for the other article is about D versus Delphi. A comparison of the two languages based upon syntax, features, ease of use and (inevitably) the pro's and cons of each language. I have a question. I read the Call to Papers and I think the piece is clear and to the point. What I do not understand however is your choices for the format that articles should be in when submitted. I understand the need to have all text in plain .txt format without any formatting, but why ask for a Word document to represent the original article? Wouldn't it be much easier if I gave you an .html file that contains a formatted version of the text? I think 'emulating' a Word document in .html is pretty difficult and chances are great the results won't be as I intended... Don't get me wrong, I know nothing about publishing and I may be totally off here, but it just seems to me it would be much more easy if I just gave you an .html file? If you told me the specification of how you want the html to be formatted, it might also save you a lot of time... Ah well, just a thought. -- Stijn OddesE_XYZ hotmail.com http://OddesE.cjb.net _________________________________________________ Remove _XYZ from my address when replying by mail
Jun 26 2002
parent "Matthew Wilson" <matthew thedjournal.com> writes:
Sorry, my fault for being vague.

The reasons for the plain-text format are, as you say, obvious. I suggested
that a submitter _may_ wish to submit a word document in order to help the
layout person see the original intent. It is entirely appropriate that a
HTML form would be equally valid.

Matthew

"OddesE" <OddesE_XYZ hotmail.com> wrote in message
news:afc9i2$12nq$1 digitaldaemon.com...
 "Matthew Wilson" <matthew thedjournal.com> wrote in message
 news:af88ii$2ptn$1 digitaldaemon.com...
 Stijn

 Excellent stuff! Thanks very much for this. I definitely want to hear


 you regarding the article ideas. For guidance, please check out
 http://thedjournal.com/papers.html

 And to everyone who has contributed so far, thanks for that. Your
 contributions have not got lost! I have to apologise, as the last two

 have been a bit of a nightmare, and this and the next will be also, but
 after that I should be getting back to the editing stuff, and will be in
 touch.

 And to everyone who has not contributed, please do so. The level of

 we have so far makes me think this is going to be very popular, so

 to stick on the resume as well as knowing you're contributing to D


 good ;)

 Matthew

Matthew, The idea for the opinion article is an article about error handling. Where to handle what kind of errors, ways to structure your code, what kind of errors should and should not be handled, error codes versus exceptions and design by contract. I also want to talk a bit about usefull error messages and preventing and detecting user errors... The idea for the other article is about D versus Delphi. A comparison of the two languages based upon syntax, features, ease of use and (inevitably) the pro's and cons of each language. I have a question. I read the Call to Papers and I think the piece is clear and to the point. What I do not understand however is your choices for the format that articles should be in when submitted. I understand the need to have all text in plain .txt format without any formatting, but why ask for a Word document to represent the original article? Wouldn't it be much easier if I gave you an .html file that contains a formatted version of the text? I think 'emulating' a Word document in .html is pretty difficult and chances are great the results won't be as I intended... Don't get me wrong, I know nothing about publishing and I may be totally off here, but it just seems to me it would be much more easy if I just gave you an .html file? If you told me the specification of how you want the html to be formatted, it might also save you a lot of time... Ah well, just a thought. -- Stijn OddesE_XYZ hotmail.com http://OddesE.cjb.net _________________________________________________ Remove _XYZ from my address when replying by mail

Jun 26 2002
prev sibling parent reply "anderson" <anderson firestar.com.au> writes:
Thanks, I've made those changes.


 Walter's stuff is not new ofcourse, but still probably
 deserves a place in the magazine.

Walter suggested this to the newgroup himself. It's in the "The D Journal" messages. It'll probably be sorted though when it's time for the journal. If the journal gets enough Notes, a whole lot will probably be placed on a reserve pile so that the notes can be kept a-refresh. A few oldies in the pack will simply act as extenders. Keep the comments comming. PS about Cohesion, could you give further details. I've always thought of cohesion as a kind of glue that makes things stick easily together (hence the name). It's a way of making things intergrate well. Anyway here's what I changed it to... "Cohesion is the way things work together. Take the car example again. The tyre needs to be able to be placed into any car without any changes made on the car itself. Low cohesion makes components less flexible/efficient together."
Jun 25 2002
parent "OddesE" <OddesE_XYZ hotmail.com> writes:
"anderson" <anderson firestar.com.au> wrote in message
news:af9f3r$1jog$1 digitaldaemon.com...
 Thanks, I've made those changes.


 Walter's stuff is not new ofcourse, but still probably
 deserves a place in the magazine.

Walter suggested this to the newgroup himself. It's in the "The D Journal" messages. It'll probably be sorted though when it's time for the journal.

 the journal gets enough Notes, a whole lot will probably be placed on a
 reserve pile so that the notes can be kept a-refresh. A few oldies in the
 pack will simply act as extenders.

Yes I remember now, you are right.
 Keep the comments comming.

 PS about Cohesion, could you give further details.

 I've always thought of cohesion as a kind of glue that makes things stick
 easily together (hence the name). It's a way of making things intergrate
 well.

 Anyway here's what I changed it to...

 "Cohesion is the way things work together. Take the car example again. The
 tyre needs to be able to be placed into any car without any changes made

 the car itself.  Low cohesion makes components less flexible/efficient
 together."

Mmm...No sorry, I can't agree with that too. You see, cohesion and coupling refer to two different aspects of a software component. Coupling refers to the interaction of the component with the outside world, such as the interaction of the tyre with the car in your example. It is usually good practice to keep this kind of interaction low. If your component is interacting with dozens of other components, it probably is dependant of those components, making it more dificult to reuse. Cohesion refers to the inside world of a component. You are right in your glue analogy here, but it is the glue that is keeping the different parts of the component itself together. How closely are different parts of a component related? Take the tyre from your example. It consists of an outer tube, an inner tube filled with air and an air valve. Any of these components alone is pretty useless, but together they form a perfectly good tyre. To get back to software, a class has high cohesion if all the fields and methods of the class clearly belong together. If you are writing a game and create a class Bitmap, with fields X, Y, Width, Height and PixelData and methods Draw, Erase, Load and Save, you would say it has high cohesion. Adding a method PlayWaveFile would break that cohesion. So Coupling refers to the outside world relative to the component and Cohesion refers to the inside world. Hope that helps... :) -- Stijn OddesE_XYZ hotmail.com http://OddesE.cjb.net _________________________________________________ Remove _XYZ from my address when replying by mail
Jun 26 2002