in vb6 we have InStr ,and in vb.net ?

  • Thread starter Thread starter Daylor
  • Start date Start date
Cor,

We all want the nonsense to stop. If your method works, great. If in 2
weeks it's worse you'll have to think of something else. :-)
 
Hi Herfried,
An MSDN page helps in more than 99% of the questions.

That's being a little over the top, just because you posted a link and no
reply was given saying that the link was helpful, does not mean that the
person was satisfied! Imagine if they said, "Hang on a minute, that was
crap, give me something else!", you would find it rude, as would I! But no
way is 99% of questions answered by MSDN links, no way on this earth!

What you meant to say is, 99% of *your* understanding of the question is
answered by MSDN links. And believe it or not, *our* understanding of
someones question is *not* always correct.
I _never_ posted code/a link to code with German variable names. I
_hate_ German variable names. As mentioned previously, IMO even code
commented in _Chinese_ may be helpful if useful variable names are
used. And I am convinced that even English speaking people who do not
understand German will find a "Download" (we use the same word like in
English) link on a German language page.

That is a very *minor* point that you have picked up on there Herfried and
that is exactly what Tom was referring to in a previous post. Variable
names do not explain code deeply enough, they might do with very simple
code, but not with the complicated stuff. Yes, German code can be
understood, you are misunderstanding what I meant, I said that people do not
always understand the German explanation that goes with it, that is all.

I love hearing things put into "layman terms", have you ever heard of that
phrase Herfried? It means that more complex things are being explained by
being compared to things that are more simple, like explaining the inside of
the Earth by looking at the inside of an apple for example. I think *those*
explanations are great and they help people far more than an MSDN link that
is riddled with Jargon and lines and lines of Americanized text.

LOL, I'd love to see an MSDN page with a scribble drawing of some
programming methodology being likened to striking a badger with a pastrami!!

Nick. :-)

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
I got fed up with programming because it's such a
hamster wheel. I'm glad I'm back, but its still a lot
of running just to stay where you are!

:-)
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
 
Hi Nick,

* "Nak said:
Tom has hit the nail on the head. If you hand someone VB code with *no*
comments they will not *always* understand it unless it has been written in
a well structured and modular fashion.

Feel free to ask for an explanation on what you don't understand.
I, as do many others like *understanding* code before I use it, when
I ask a question in here, I do not want someone to search on Google
for me,

There are hundreds of users who do not even know that they can use
Google to find a solution.
I want someone to explain the workings behind something.

That's your personal preference.
Once I have understood the workings behind code
I can quickly change and implement it in a way that best suits me, this is
the way that *I* personally like to program. I am not a copy and paste
programmer, if I use someone else's code I *always* rewrite it so that I can
understand it from the ground up.

_You_ are not a copy-paste programmer. _I_ am not a copy-paste
programmer too. Nobody should be a copy-paste programmer.
Nevertheless, if I want a solution for a problem I am asking for source
code that solves the problem. If I have the code, I try to understand
it. There maybe people who do not want to understand the code.
So when you get a link to code that is written badly but has lots of
comments, the comments have to be in a language that the particular person
understands, and I have *never* once seen *anyone* ask,

Your personal preference. As mentioned previosly, I would even like to
get code commented in Chinese if it's the only code I could find to
solve the problem.
Why do we not ask? Because this is an English speaking newsgroup. As
Cor has so nicely pointed out, there *are* localised alternatives.

I never saw somebody talking German or an other non-English language
here.
There is no point what so ever in communicating in any other language in a newsgroup
other than it's native language. Herfried is so quick to tell people where
to go if they are asking questions related to another *programming*
language, but he never tells people to go to German newsgroups if they are
speaking German!

There were never people who wanted to speak German. And if there were
people asking questions in Italian or French, I gave them a link to the
appropriate group in their language.
That just goes to show a blatant flexing of authority, and believe it or
not Herfried, you *are* the "regular of regulars" because you post more
replies in here than *any* one else, is that clear? because it is as clear
as broad daylight to me, as it is *many* others.

Thanks for clarifying that. I didn't understand the meaning of "regular
of regulars" before (I misinterpreted it, sorry).
I was not saying that Herfried is not helpful, because he is, but not
all the time. Just because someone offers help that does not make them
"helpful", that is *not* the definition of helpful. Imagine sitting in a
lecture hall in a University and someone goes to ask the lecturer a
question, the lecturer answers with one line,

"Turn to page 23"

That is *not* being helpful all the time. Some times it is, when
someone wants a quick example of how to do something quite menial.

That's a big problem, I know. There are people posting with various
backgrounds: beginners, professionals, etc.

It's hard to decide if the solution I/any other person will help the
OP. But the OP can reply if he has problems in understanding the
solution provided.
But allot of the time people want to do things that are more complicated and
they want to get a deeper understanding, only then will explanation and
conversation rule the day.

ACK. My Englishg-typing isn't that fast, that's why I do not provide an
explanation that will help a _beginner_ if the question may be written
by a professional who only needs the name of a property or its
description on the MSDN documentation. If a beginner doesn't understand
the linked documentation, he is free to ask for an explanation. Time is
rare and I won't do any unnecessary work.
I, as have *many* others, asked questions in here that have not even
been answered, simply because they require more time and forethought, this
is a shame, but tough luck because at the end of the day this newsgroup does
not hold *all* of the answers :-(
:-(

I could imagine the translation system that is used in Ultima Online
being used in a newsgroup, imagine that, a newsgroup where *everything* is
translated into your native language, no matter what it may be! Marvellous
bit of technology and forethought!

Maybe we will start research on this topic on university.

;-)))

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
<http://www.mvps.org/dotnet>

Improve your quoting style:
<http://learn.to/quote>
<http://www.plig.net/nnq/nquote.html>
 
Hi Herfried,
Feel free to ask for an explanation on what you don't understand.

I *always* do, I'm most annoying like that!
That's your personal preference.

Yes, that is why I prefixed the sentence with "I".
I never saw somebody talking German or an other non-English language
here.

That is surprising, I have, LOL and *no* I am not going to search for an
example!! I very rarely scroll the list down :-(
Thanks for clarifying that. I didn't understand the meaning of "regular
of regulars" before (I misinterpreted it, sorry).

No problems, and no apology needed.
That's a big problem, I know. There are people posting with various
backgrounds: beginners, professionals, etc.
It's hard to decide if the solution I/any other person will help the
OP. But the OP can reply if he has problems in understanding the
solution provided.

Yes that is most true. But you will always find one thing, that successful
teachers will *always* treat people as if they are on the same level of
understanding. Otherwise teaching many people at once would just not work
:-(

LOL So basically Herfried, you *should* be treating every new person that
asks a questions as a complete idiot! Because if you do not know their
level of understanding you *should* presume that they have none. That is
how most books are written, unless strictly expressed otherwise in the
preface.
ACK. My Englishg-typing isn't that fast, that's why I do not provide an
explanation that will help a _beginner_ if the question may be written
by a professional who only needs the name of a property or its
description on the MSDN documentation. If a beginner doesn't understand
the linked documentation, he is free to ask for an explanation. Time is
rare and I won't do any unnecessary work.

ACK to you too, and also,

~~ "Quantity *not* Quality" ~~
Maybe we will start research on this topic on university.

That would be cool, I believe it is called Systran, or something like that.
I wish I had the chance to go to University, lucky bugger!

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
I got fed up with programming because it's such a
hamster wheel. I'm glad I'm back, but its still a lot
of running just to stay where you are!

:-)
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
 
* "Nak said:
That's being a little over the top, just because you posted a link and no
reply was given saying that the link was helpful, does not mean that the
person was satisfied!

I used the "99%" methaphorically. You don't even get a reply for every
long explanation. Sometimes a link to the MSDN may not help directly,
but I think it's more important to _point_ somebody into the right
direction than summing up the explanation provided in the MSDN
documentation.

That's _my_ personal thought. Other people prefer answering by
providing a long explanation. I like that. If the user only wants to
ger a quick pointer, he/she will get help here. If he/she will get help
here too. Let's provide the best support here for everybody.
Imagine if they said, "Hang on a minute, that was
crap, give me something else!", you would find it rude, as would I! But no
way is 99% of questions answered by MSDN links, no way on this earth!
;-)

What you meant to say is, 99% of *your* understanding of the question is
answered by MSDN links. And believe it or not, *our* understanding of
someones question is *not* always correct.

I know that. Nevertheless the link is useful. I think some users may
have made their first experiences with the MSDN documentation by
following a link. Others may have found a useful sample on the MSDN
documentation page. Others may have found keywords to be used for
further recherche (is that the right word?).
That is a very *minor* point that you have picked up on there Herfried and
that is exactly what Tom was referring to in a previous post. Variable
names do not explain code deeply enough, they might do with very
simple

This depends on the code. If I want a component to store user settings,
I don't need to understand the code. I handle the component as a black
box and use the binary.
code, but not with the complicated stuff. Yes, German code can be
understood, you are misunderstanding what I meant, I said that people do not
always understand the German explanation that goes with it, that is all.

OK, I fully agree with you in this point.
I love hearing things put into "layman terms", have you ever heard of that
phrase Herfried?

I heard it. It's used a similar phrase in German too. But not
everybody here is a layman. There are professionals looking for help
too. This is neither a beginner's newsgroup by definition nor a
professional's newsgroup. It's a newsgroup for _any_ VB.NET user.
It means that more complex things are being explained by
being compared to things that are more simple, like explaining the inside of
the Earth by looking at the inside of an apple for example. I think *those*
explanations are great and they help people far more than an MSDN link that
is riddled with Jargon and lines and lines of Americanized text.

LOL, you as a native English speaker say that. The MSDN documentation is
very helpful for me and it's the first pointer I have when looking for a
solution. Then I use Google Groups Search. I doubt that all people who
post questions here know about MSDN documentation and Google Groups
Search. Or they don't know the right keywords.
LOL, I'd love to see an MSDN page with a scribble drawing of some
programming methodology being likened to striking a badger with a pastrami!!
:-)))

Nick. :-)

:-)

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
<http://www.mvps.org/dotnet>

Improve your quoting style:
<http://learn.to/quote>
<http://www.plig.net/nnq/nquote.html>
 
Herfried K. Wagner said:
Sorry, that's nonsense. I do not want to psychoanalyze people in a
technical group. There are other newsgroups which are related to
psychology etc.

Actually I'm sorry but it isn't nonsense. It isn't psychoanalysis... we
call it common sense. Like when you use the word "psychoanalyze" and then
claim to not understand (or be able to find the definition of) "dopey."
Who's zooming who as we say?
You missed the point: Everybody can add a quote to her/his posts. And
there are language barriers, have a look at Cor's explanation.

One more time... It is you (simply count the number of people who have
posted this) is missing the point.

When I point you to a message that explains what you are doing you ignore
the original post any my mention of it. Now you want to use a post from Cor
in your own defense. It is the "defense" that has everybody irritated. Not
"angry" just frustrated...

It has been pointed out that your responses while massive in quantity don't
impact people exactly the way you think they should. You ignored a
perfectly reasonable response... why? Well we can't know but surely
something is up and it isn't technical in nature.
An MSDN page helps in more than 99% of the questions.

They do not. But I'll bite where did you get your numbers from? If they
answer more than 5% of the questions I would be surprised but that still
isn't the point. Conversations aid in understanding, an MSDN page will
never substitute for human interaction.
I rarely post links to German pages, even not to explanations which are
written in German because that doesn't male sense. Nevertheless, VB.NET
code which is commented in German can be helpful.

ONE MORE TIME... he wasn't only talking about German pages. But that is a h
andy thing for you to continue to harp on. Find my example where I wrote
that if somebody claimed you did something 20 times you would just count
them and say "no only 18 times" rather than address the 18 times.

Let me point something out since you seem particularly unaware of the
fact... your antics are losing you ground.
Sorry, I don't understand what you mean.

Oh look there it is... and lo and behold you don't understand. How
convenient... now you look that word up and claim that Google doesn't define
it either. I know your game and it isn't working.
I _never_ posted code/a link to code with German variable names. I
_hate_ German variable names. As mentioned previously, IMO even code
commented in _Chinese_ may be helpful if useful variable names are
used. And I am convinced that even English speaking people who do not
understand German will find a "Download" (we use the same word like in
English) link on a German language page.

Sure you're convinced, I might even be convinced but a reader of this
newsgroup wrote that he wasn't. How hard can it be to understand that you
aren't the only person with a valid opinion?

The ball's in your court
 
Herfried K. Wagner said:
Feel free to ask for an explanation on what you don't understand.

Feel free not to offer a reply to every question posted if you don't have
the time to explain something.
There are hundreds of users who do not even know that they can use
Google to find a solution.

Then one solution is to ask "Have you tried searching Google?" See how that
works?
 
* "Nak said:
I *always* do, I'm most annoying like that!

I don't think that asking a question is annoying.

:-)
Yes, that is why I prefixed the sentence with "I".
:-)


Yes that is most true. But you will always find one thing, that successful
teachers will *always* treat people as if they are on the same level of
understanding. Otherwise teaching many people at once would just not work
:-(

That's why I think that a short answer and an explanation complement
each other (is that the right term?).
LOL So basically Herfried, you *should* be treating every new person that
asks a questions as a complete idiot! Because if you do not know their
level of understanding you *should* presume that they have none. That is
how most books are written, unless strictly expressed otherwise in the
preface.

I know that there are other people who like to provide a long
explanation of things. I want to say thanks to them for doing that. I
provide the pointers.

;-)
ACK to you too, and also,

~~ "Quantity *not* Quality" ~~

A pointer can have a high quality too.
That would be cool, I believe it is called Systran, or something like that.
I wish I had the chance to go to University, lucky bugger!

;-)
 
* "Tom Leylan said:
Actually I'm sorry but it isn't nonsense. It isn't psychoanalysis... we
call it common sense. Like when you use the word "psychoanalyze" and then
claim to not understand (or be able to find the definition of) "dopey."
Who's zooming who as we say?

LOL. I was not sure if the term "psychoanalyze" is valid English. In
German we use "psychoanalysieren". In German, there is no similar word
to "dopey".
One more time... It is you (simply count the number of people who have
posted this) is missing the point.

It's not only you who is missing the point of my messages too.
isn't the point. Conversations aid in understanding, an MSDN page will
never substitute for human interaction.

If I am looking for a solution for a technical problem, I don't
need/want human interaction. I want a solution. People who want
interaction should look for friends or a chatroom.
ONE MORE TIME... he wasn't only talking about German pages. But that is a h
andy thing for you to continue to harp on. Find my example where I wrote
that if somebody claimed you did something 20 times you would just count
them and say "no only 18 times" rather than address the 18 times.

Sorry, I still do not understand what you mean. You should try to
explain it to somebody who isn't as good in English as _you_ are.
Sure you're convinced, I might even be convinced but a reader of this
newsgroup wrote that he wasn't. How hard can it be to understand that you
aren't the only person with a valid opinion?

I never claimed that. Other people claim that.

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
<http://www.mvps.org/dotnet>

Improve your quoting style:
<http://learn.to/quote>
<http://www.plig.net/nnq/nquote.html>
 
Nak said:
What you meant to say is, 99% of *your* understanding of the question is
answered by MSDN links. And believe it or not, *our* understanding of
someones question is *not* always correct.

Hi Nick... I don't mean to post a lot of personal facts about myself but I
wrote my first program in 1975 (or 1976) and I still can't understand half
the MSDN pages. I downloaded MSDE the other day and the MSDN page has
branches for this and branches for that. And, when it is finally installed
it doesn't handle SQL Server authentication until (you guessed it) somebody
pointed me to another page with the instructions on how to patch the
registry of all things.

If after 25+ years of software development across a dozen operating system
(I patched my CP/M bios in 8086 assembly language) in some 6 or 7 languages
I can't make heads or tails of the average MSDN page then (and I could sure
be wrong but) I have to guess the person who started learning .Net earlier
this year must be having major problems.

Tom
 
* "Tom Leylan said:
Feel free not to offer a reply to every question posted if you don't have
the time to explain something.

It seems that you didn't understand the sense of a public "support"
newsgroup.
Then one solution is to ask "Have you tried searching Google?" See how that
works?

Why should I do that? There may be no solution to the problem or the OP
doesn't know the right words to look for.

I will continue my work in this group the same way I did before. I
won't stop to do that only because some people here seem to be
enviously. It's willingness to share knowledge that counts, not sharing
personal preferences.

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
<http://www.mvps.org/dotnet>

Improve your quoting style:
<http://learn.to/quote>
<http://www.plig.net/nnq/nquote.html>
 
* "Tom Leylan said:
Hi Nick... I don't mean to post a lot of personal facts about myself but I
wrote my first program in 1975 (or 1976) and I still can't understand half
the MSDN pages. I downloaded MSDE the other day and the MSDN page has
branches for this and branches for that. And, when it is finally installed
it doesn't handle SQL Server authentication until (you guessed it) somebody
pointed me to another page with the instructions on how to patch the
registry of all things.

Wow... you are cool.
If after 25+ years of software development across a dozen operating system
(I patched my CP/M bios in 8086 assembly language) in some 6 or 7 languages
I can't make heads or tails of the average MSDN page then (and I could sure
be wrong but) I have to guess the person who started learning .Net earlier
this year must be having major problems.

I learned VB.NET with the MSDN documentation. It worked. If it doesn't
help _you_, you cannot imply that everybody has a problem understanding
MSDN pages.

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
<http://www.mvps.org/dotnet>

Improve your quoting style:
<http://learn.to/quote>
<http://www.plig.net/nnq/nquote.html>
 
Hi Tom,
Hi Nick... I don't mean to post a lot of personal facts about myself but I
wrote my first program in 1975 (or 1976) and I still can't understand half
the MSDN pages. I downloaded MSDE the other day and the MSDN page has
branches for this and branches for that. And, when it is finally
installed...

I really can't get to grips with the style of language that is used. It is
*very* Americanized, it completely does my head in. Allot of *something* is
said about *nothing*! Jargon after jargon, when jargon isn't always
necessary! I bet there is a Jargon word for scratching your ar*e!! And it
is probably something like "Rectal-dermal handling", something that when
explained to a beginner is actually harder to explain than simply saying "It
means scratching your ar*e mate!!".
it doesn't handle SQL Server authentication until (you guessed it) somebody
pointed me to another page with the instructions on how to patch the
registry of all things.

Typical!! I have had allot of annoy software related issues lately, like
when I downloaded and installed the DirectX 9 SDK, it took me 2 days to get
the managed drivers to install correctly. Guess what the solution was? I
had to run windows update, as they had magically appeared in there!!! No
one in the DirectX newsgroup knew the answer! And no MSDN site offered the
solution either!
If after 25+ years of software development across a dozen operating system
(I patched my CP/M bios in 8086 assembly language) in some 6 or 7 languages
I can't make heads or tails of the average MSDN page then (and I could sure
be wrong but) I have to guess the person who started learning .Net earlier
this year must be having major problems.

It sounds like you are very experienced, is this a Jargon thing with you
too? I suspect in the past there wasn't so much Jargon as there is now, it
is weird how something meant to simplify things actually confuses things.
What MSDN needs is a link for every Jargon word used to popup a browser
window explaining the word in layman terms!

I know exactly what you mean though, very frustrating indeed!! And there is
nothing wrong with quoting personal facts, be proud of them, I would if I
had any! ;-)

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
I got fed up with programming because it's such a
hamster wheel. I'm glad I'm back, but its still a lot
of running just to stay where you are!

:-)
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
 
* "Nak said:
I really can't get to grips with the style of language that is used. It is
*very* Americanized, it completely does my head in. Allot of *something* is
said about *nothing*! Jargon after jargon, when jargon isn't always

I would never have thought that English speaking people have more
problems reading an English MSDN version than German speaking people.
Typical!! I have had allot of annoy software related issues lately, like
when I downloaded and installed the DirectX 9 SDK, it took me 2 days to get
the managed drivers to install correctly. Guess what the solution was? I
had to run windows update, as they had magically appeared in there!!! No
one in the DirectX newsgroup knew the answer! And no MSDN site offered the
solution either!

Parts of the documentation are poor. The Framework documentation is IMO
OK.

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
<http://www.mvps.org/dotnet>

Improve your quoting style:
<http://learn.to/quote>
<http://www.plig.net/nnq/nquote.html>
 
Nak said:
Jargon after jargon, when jargon isn't always
necessary! I bet there is a Jargon word for scratching your ar*e!! And it
is probably something like "Rectal-dermal handling"

That's exactly it. I liken it to many authoritative computer books... they
speak volumes on the theory but never present a single practical example. I
suspect some of the authors have never actually finished a project, it's in
a perpetual planning stage.
I suspect in the past there wasn't so much Jargon as there is now, it
is weird how something meant to simplify things actually confuses things.

I'll grant that things are more complex than in my 1.0 MHz 8-bit CPU days
(that isn't 1.0 GHz btw) but I do tend to think much of the literature is
overly complex. One might even call it "overtly" complex in that I suspect
they do some of it on purpose. That said I realize it isn't "easy" to
explain everything to everybody...
What MSDN needs is a link for every Jargon word used to popup a browser
window explaining the word in layman terms!

That could help... the collection of "what one needs to know" is growing
exponentially though.
 
Herfried,
I would never have thought that English speaking people have more
problems reading an English MSDN version than German speaking people.

Strangely enough *you* represent a very small percentage of Germany, so you
cannot make those statements. Yes I can read the text, yes I can write text
that is grammatically correct, yes I can understand *all* English very well.
But I hate jargon text, and the majority of jargon is American
unfortunately. So no, German people cannot understand it more than English
people, I was not speaking on behalf of every English person, just my
personal opinion that jargon does *not* simplify things!
Parts of the documentation are poor. The Framework documentation is IMO
OK.

*OK* That says it all.

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
I got fed up with programming because it's such a
hamster wheel. I'm glad I'm back, but its still a lot
of running just to stay where you are!

:-)
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
 
Herfried,
I will continue my work in this group the same way I did before. I
won't stop to do that only because some people here seem to be
enviously.

No one is envious of you Herfried.

I don't think many people could possibly be envious of you simply because
you have an archive of MSDN links! It is very simple to provide help the
way that you do, you have even admitted it yourself. In order for someone
to be envious of you, you would have to be doing something that they cannot.
It's willingness to share knowledge that counts, not sharing personal
preferences.

Actually Herfried, not everyone comes here to have a pre defined answer, as
you well know, every programmer is unique and has a unique style. That is
what the newsgroup offers, everyone to chip in their own unique style which
depends completely on personal preferences. When providing an answer,
should you give the most simple solution or the most advanced solution,
sometimes both, that is a decision that people make when they answer
questions.

When I first started programming I used to refer to Planet Source Code. The
web site is designed for beginners and professionals alike, that is why I
used to like it. It was also a major incentive to be able to get kudos for
your hard efforts, it actively encourages sharing of source code. My point
is that on PSC you will find a million and 1 examples saying how to do the
same thing, all with unique styles. I hunt for a while until I find an
example that suits the style that I am after. If all examples were the same
PSC would not be popular, it would be another MSDN.

Believe it or not, even you apply your own personal preferences when you
answer questions Herfried, even you.

Anyways, that is enough of this thread for me, Pastrim Leader signing out!
;-)

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
I got fed up with programming because it's such a
hamster wheel. I'm glad I'm back, but its still a lot
of running just to stay where you are!

:-)
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
 
Hi Nick

Herfried is not from Germany.

Not everybody who speaks English is from England, that is the same with the
German language.

:-))

Cor
 
Hi Nick,

When I was already a while programming I got to do with Burroughs.

I think that they are from Calfornia. I had learned English (here it was
only Oxford English) and had read a lot from IBM.

But it was nice to read that English and than thinking you where walking in
the Mexico sun. But it was correct English, only not used in the City.

:-))

Cor
 
Back
Top