what is wrong with this

[free2cric]

Hi,
I have declared pointer of pointers **a;
so In a loop I assign a block to a pointer and put a value in it
and then I want to print these values.

My following program doesnt work.

Also How to do same program with int *a[]; (array of pointers).
Any help would really help.

#include <stdio.h>
#include <conio.h>
#include <malloc.h>

void main()
{
int **a;
int v=0;

for (v=0;v<5;v++)
{
*(a+v)=(int *)malloc(sizeof(int));
**(a+v)=v;
}

for (v=0;v<5;v++)
{
printf("%d\n",**(a+v));
}

exit(0);

}

[A. Sinan Unur]

fr*******@yahoo.com wrote in news:1140783951.891486.192110
@t39g2000cwt.googlegroups.com:

Any help would really help.
OK, then.
#include <stdio.h>
#include <conio.h>
conio.h is a non-standard header. Don't see any need for any nonstandard
constructs below, so omit this.
#include <malloc.h>
malloc.h is a non-standard header. You should:

#include <stdlib.h>

for malloc.
void main()
This is a non-standard prototype for main. In this case, you should use:

int main(void)
{
int **a;
int v=0;

for (v=0;v<5;v++)
{
*(a+v)=(int *)malloc(sizeof(int));
Don't cast the return value of malloc. It can hide failure to include
stdlib.h.
**(a+v)=v;
BAM! a itself points to nowhere. It should point to a chunk of memory
large enough to hold exactly five pointers to int.
}

for (v=0;v<5;v++)
{
printf("%d\n",**(a+v));
}

exit(0);

return 0;
}

is more conventional.

Sinan
--
--
A. Sinan Unur <1u**@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)

[pranav.choudhary]

Perhaps i know where you have got this wrong. You declared
int **a;
can you read the above declaration, what does it say?? It says "a is a
pointer to pointer to int". So a is large enough to hold one pointer to
integer. But in your code you assume it large enough to hold 5 pointers
to integer, ie. a is not an array of 5 pointers to int, but just a
(single)pointer to pointer to int. To make your program work we have to
say

int **a;
a = (int **)malloc(5 *sizeof(int *));

I hope things are clear now.

[A. Sinan Unur]

"pr**************@gmail.com" <pr**************@gmail.com> wrote in
news:11**********************@i40g2000cwc.googlegr oups.com:

Perhaps i know where you have got this wrong.
Who got what wrong? See <URL:http://cfaj.freeshell.org/google/>
int **a;
a = (int **)malloc(5 *sizeof(int *));
#include <stdlib.h>

int **a = malloc(5 * sizeof(*a));

if ( a ) {

}

Casting the return value of malloc can hide errors due to failure to
include stdlib.h.

By using the form above, the malloc call remains the same even if you
change the type of a.
I hope things are clear now.

Not really.

Sinan

--
A. Sinan Unur <1u**@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)

[pranav.choudhary]

I agree with that. My mail was not in reply to yours but to the
original mail. There was something else that was wrong with the posted
code and not the issue of not being able to include a header file. The
guy was simply treatin int **a; as int *a[5];

[Richard Bos]

"pr**************@gmail.com" <pr**************@gmail.com> wrote:

I agree with that.
With _what_? Learn to tell Google Broken Beta to post with context, or
get a newsreader.
My mail was not in reply to yours but to the original mail.

There are no mails. There are only posts. Usenet is not an e-mail
service. Usenet is not the property of Google "do evil" Inc. Usenet is
an international network of newsgroups, with their own netiquette, far
preceeding the existence of Google. Learn to use it properly, please.

Richard

[Richard G. Riley]

On 2006-02-24, fr*******@yahoo.com <fr*******@yahoo.com> wrote:

Hi,
I have declared pointer of pointers **a;
so In a loop I assign a block to a pointer and put a value in it
and then I want to print these values.

My following program doesnt work.

Also How to do same program with int *a[]; (array of pointers).
Any help would really help.

#include <stdio.h>
#include <conio.h>
#include <malloc.h>

void main()
{
int **a;
int v=0;

for (v=0;v<5;v++)
{
*(a+v)=(int *)malloc(sizeof(int));
You have not yet allocated an area of memory to store your int
pointers. a is pointing to nothing valid.

There are other horrible things there too but if you get the
first bit right, the rest should logically follow as you get to grips
with pointers and pointers to pointers. Good luck!
**(a+v)=v;
}

for (v=0;v<5;v++)
{
printf("%d\n",**(a+v));
}

exit(0);

}

--
Remove evomer to reply

[CBFalconer]

fr*******@yahoo.com wrote:

I have declared pointer of pointers **a;
so In a loop I assign a block to a pointer and put a value in it
and then I want to print these values.

My following program doesnt work.

Also How to do same program with int *a[]; (array of pointers).
Any help would really help.

#include <stdio.h>
#include <conio.h>
no such standard include file. Remove this.
#include <malloc.h>
No such standard include file. You probably want stdlib.h

void main()
All bets are off. main returns int. Say so.
{
int **a;
int v=0;

for (v=0;v<5;v++)
The use of blanks is allowed, and adds legibility. No extra charge
is made for them.

for (v = 0; v < 5; v++)
etc.
{
*(a+v)=(int *)malloc(sizeof(int));
Do not cast the return value of malloc. It only hides errors.
Besides, how can the left side, which has no associated memory,
hold the result? a has been defined to hold one single pointer to
a pointer to an int, and has never been initialized. Who knows
what (a + v) refers to. Even if the program somehow survived the
earlier gross errors, this made it go KA-BOOM. The approved way to
use malloc is:

ptr = malloc(SOMENUMBER * sizeof *ptr);

followed by checking for success, i.e. (ptr != NULL). Note that
the *s above are not the same thing, one is a multiplicative
operator, and one is a dereferencing operator.

In your case you would need multiple mallocs, something like:

if (a = malloc(5 * sizeof *a)) {
for (n = 0; n < 5; n++) {
if (*(a + n) = malloc(sizeof *(a + n))) {
/* now you have a place to store an int */
}
else handlemallocfailure();
}
else handlemallocfailure();

and somewhere there should be a define for the magic number 5.
**(a+v)=v;
}
for (v=0;v<5;v++)
{
printf("%d\n",**(a+v));
}
exit(0);
}

If you want to post a followup via groups.google.com, don't use the
broken "Reply" link at the bottom of the article. Click on "show
options" at the top of the article, then click on the "Reply" at
the bottom of the article headers.

More details at: <http://cfaj.freeshell.org/google/>
Also see <http://www.safalra.com/special/googlegroupsreply/>

--
Some informative links:
news:news.announce.newusers
http://www.geocities.com/nnqweb/
http://www.catb.org/~esr/faqs/smart-questions.html
http://www.caliburn.nl/topposting.html
http://www.netmeister.org/news/learn2quote.html

[Keith Thompson]

rl*@hoekstra-uitgeverij.nl (Richard Bos) writes:
[...]

There are no mails. There are only posts. Usenet is not an e-mail
service. Usenet is not the property of Google "do evil" Inc. Usenet is
an international network of newsgroups, with their own netiquette, far
preceeding the existence of Google. Learn to use it properly, please.

.... by reading <http://cfaj.freeshell.org/google/>.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

[free2cric]

ok guys whaterver u told , it helped me..
but who will free the allocated memory.. ur fathers????
Keith Thompson wrote:

rl*@hoekstra-uitgeverij.nl (Richard Bos) writes:
[...]

There are no mails. There are only posts. Usenet is not an e-mail
service. Usenet is not the property of Google "do evil" Inc. Usenet is
an international network of newsgroups, with their own netiquette, far
preceeding the existence of Google. Learn to use it properly, please.

... by reading <http://cfaj.freeshell.org/google/>.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

[pete]

fr*******@yahoo.com wrote:

ur fathers????

abraham and lot.

--
pete

[Flash Gordon]

fr*******@yahoo.com wrote:

Your response belongs *under* the text you are replying to, not above it.

ok guys whaterver u told , it helped me..
Please don't use contractions like "u" you "you" and "ur" for "your". It
makes it *far* harder for others to read what you are saying. In
general, since you want people to help you be nice to them by writing
properly or why should we put in the effort to solve your problems?
but who will free the allocated memory.. ur fathers????

<snip>

If you allocate memory it is up to you to deallocate it. That's why
there is a free function as well as malloc and realloc.
--
Flash Gordon, living in interesting times.
Web site - http://home.flash-gordon.me.uk/
comp.lang.c posting guidelines and intro:
http://clc-wiki.net/wiki/Intro_to_clc

[free2cric]

Flash Gordon

Please don't use contractions like "u" you "you" and "ur" for "your". It
makes it *far* harder for others to read what you are saying.

I dont udenrstand why people can not understand "u" and "ur"
If you can understand C, C++ and complicated coding then its very easy
to understand
i which context "u" and "ur" is used. We are not writing the post to
mr. president to be so correct.

Thanks anyway for your feedback.

bye
cric.

[Vladimir S. Oka]

fr*******@yahoo.com wrote:

Flash Gordon

Please don't use contractions like "u" you "you" and "ur" for "your".
It makes it *far* harder for others to read what you are saying.

I dont udenrstand why people can not understand "u" and "ur"
If you can understand C, C++ and complicated coding then its very easy
to understand
i which context "u" and "ur" is used. We are not writing the post to
mr. president to be so correct.

I'm sure Mr. President wouldn't be happy at your lack of respect.

Silly phonetic abbreviations can be /very/ hard for non-native English
speakers to decode. I'm sure you do have some consideration (if not
respect) for them, don't you? Otherwise: Hau vud ju lajk if aj vrote in
vot aj konsider tu be fonetik ingliš?

Even for native or fluent English speakers they require extra effort to
decode (unless they learned it from age 3, I guess).

Also, /especially/ people who /really/ understand C (C++ is off-topic,
and not necessarily well understood in these parts), live and breathe
syntax correctness, and "u" and "ur" are certainly not correct English
syntax (also, look up "ur" in any German dictionary; C does not support
mixed language programming either).

Hope this clarifies this a little bit for you.

--
BR, Vladimir

From a certain point onward there is no longer any turning back.
That is the point that must be reached.
-- F. Kafka

[websnarf]

fr*******@yahoo.com wrote:

I have declared pointer of pointers **a;
so In a loop I assign a block to a pointer and put a value in it
and then I want to print these values.

My following program doesnt work.

Also How to do same program with int *a[]; (array of pointers).
Any help would really help.

#include <stdio.h>
#include <conio.h>
#include <malloc.h>

void main() {
int **a;
int v=0;

for (v=0;v<5;v++) {
*(a+v)=(int *)malloc(sizeof(int));
**(a+v)=v;
}

for (v=0;v<5;v++) {
printf("%d\n",**(a+v));
}
exit(0);
}

You are missing the "backbone" allocation. int ** a, is a pointer to
storage which itself points to additional storage for each integer.
You've allocated the storage for each integer, but not to the big
structure to hold these pointers.

If your compiler has good warnings, you could try to crank the warning
levels up and it should tell you that the line with *(a+v) = ... is
writing to the other end of (a+v) without that pointer having
initilizing it. It seems to me that you have to put something like:

a = (int **) malloc (5 * sizeof (int *));

at the beginning.

Remember that each * in your declaration requires you to point that
level at some storage (or to malloc it) directly in your code, while
each [] in your declaration implicitely declares its own storage for
that level (but may require you to calculate the sizeof() in mallocs at
higher levels carefully).

--
Paul Hsieh
http://www.pobox.com/~qed/
http://bstring.sf.net/

[Richard Bos]

fr*******@yahoo.com wrote:

Flash Gordon

Please don't use contractions like "u" you "you" and "ur" for "your". It
makes it *far* harder for others to read what you are saying.

I dont udenrstand why people can not understand "u" and "ur"
If you can understand C, C++ and complicated coding then its very easy
to understand
i which context "u" and "ur" is used. We are not writing the post to
mr. president to be so correct.

Congratulations: you are now officially too stupid to help.

Richard

[Keith Thompson]

rl*@hoekstra-uitgeverij.nl (Richard Bos) writes:

fr*******@yahoo.com wrote:

Flash Gordon

> Please don't use contractions like "u" you "you" and "ur" for "your". It
> makes it *far* harder for others to read what you are saying.

I dont udenrstand why people can not understand "u" and "ur"
If you can understand C, C++ and complicated coding then its very easy
to understand
i which context "u" and "ur" is used. We are not writing the post to
mr. president to be so correct.

Congratulations: you are now officially too stupid to help.

I suggest giving "free2cric" a break, at least tentatively. He admits
not understanding the problem; it's entirely possible that he's
capable of learning. (Even though he's been posting sporadically to
comp.lang.c for over a year, he might have missed the repeated
discussions of why silly abbreviations are a bad idea.)

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

[Richard G. Riley]

On 2006-02-27, Vladimir S. Oka <no****@btopenworld.com> wrote:

fr*******@yahoo.com wrote:
Silly phonetic abbreviations can be /very/ hard for non-native English
speakers to decode. I'm sure you do have some consideration (if not
respect) for them, don't you? Otherwise: Hau vud ju lajk if aj vrote in
vot aj konsider tu be fonetik ingli??

Even for native or fluent English speakers they require extra effort to
decode (unless they learned it from age 3, I guess).

Also, /especially/ people who /really/ understand C (C++ is
off-topic,
In many circles constant /hiliting/ is seen as obnoxious and
boring. It lights my newsreader like a beacon and for those that don't
support it, it breaks up the English. Please refrain from doing it so
frequently. It is really, really nasty.

and not necessarily well understood in these parts), live and breathe
syntax correctness, and "u" and "ur" are certainly not correct English
syntax (also, look up "ur" in any German dictionary; C does not support
mixed language programming either).

Hope this clarifies this a little bit for you.

[August Karlstrom]

fr*******@yahoo.com wrote:

Hi,
I have declared pointer of pointers **a;
so In a loop I assign a block to a pointer and put a value in it
and then I want to print these values.

My following program doesnt work.

Also How to do same program with int *a[]; (array of pointers).
Any help would really help.

#include <stdio.h>
#include <conio.h>
#include <malloc.h>

void main()
{
int **a;
int v=0;

for (v=0;v<5;v++)
{
*(a+v)=(int *)malloc(sizeof(int));
**(a+v)=v;
}

for (v=0;v<5;v++)
{
printf("%d\n",**(a+v));
}

exit(0);

}

You probably want something like the following.

#include <stdio.h>
#include <stdlib.h>

#define LEN 5

int main(void)
{
int **a;
int k = 0;

a = malloc(sizeof *a);
a[0] = malloc(LEN * sizeof **a);
for (k = 0; k < LEN; k++) { a[0][k] = k; }
for (k = 0; k < LEN; k++) { printf("%d\n", a[0][k]); }
return 0;
}
August

--
I am the "ILOVEGNU" signature virus. Just copy me to your
signature. This email was infected under the terms of the GNU
General Public License.

[Flash Gordon]

Vladimir S. Oka wrote:

fr*******@yahoo.com wrote:

Flash Gordon

Please don't use contractions like "u" you "you" and "ur" for "your".
It makes it *far* harder for others to read what you are saying.

I dont udenrstand why people can not understand "u" and "ur"
If you can understand C, C++ and complicated coding then its very easy
to understand
i which context "u" and "ur" is used. We are not writing the post to
mr. president to be so correct.

I'm sure Mr. President wouldn't be happy at your lack of respect.

Silly phonetic abbreviations can be /very/ hard for non-native English
speakers to decode. I'm sure you do have some consideration (if not

<snip>

They are also very difficult for certain groups of *native* English
speakers, such as dyslexics (i.e. me). I, for example, will often have
to read a paragraph using those contractions at least twice before I
understand it, the second time much more slowly than normal. If they are
used more that a couple of times I might have to read it several times
because by the time I've decoded "ur" as "your" I've forgotten the rest
of the paragraph.

Given enough *years* of exposure, or months of *real* effort, it is
possible I might become fluent in such contractions. However, unless
someone is going to pay me a *lot* of money to do something that for me
is far harder than programming and which I do not enjoy at all, then I'm
not going to learn these contractions until they have been used in
normal English for several years.
--
Flash Gordon, living in interesting times.
Web site - http://home.flash-gordon.me.uk/
comp.lang.c posting guidelines and intro:
http://clc-wiki.net/wiki/Intro_to_clc

[Micah Cowan]

"Richard G. Riley" <rg****@gmail.com> writes:

On 2006-02-27, Vladimir S. Oka <no****@btopenworld.com> wrote:

fr*******@yahoo.com wrote:

Silly phonetic abbreviations can be /very/ hard for non-native English
speakers to decode. I'm sure you do have some consideration (if not
respect) for them, don't you? Otherwise: Hau vud ju lajk if aj vrote in
vot aj konsider tu be fonetik ingli??

Even for native or fluent English speakers they require extra effort to
decode (unless they learned it from age 3, I guess).

Also, /especially/ people who /really/ understand C (C++ is
off-topic,

In many circles constant /hiliting/ is seen as obnoxious and
boring. It lights my newsreader like a beacon and for those that don't
support it, it breaks up the English. Please refrain from doing it so
frequently. It is really, really nasty.

He did no hiliting whatsoever. Any hiliting done is solely from your
newsreader. If you don't like it, see if you can turn it off.

As to the comment about it's handling in newsreaders that "don't
support it": the conventions for denoting /italics/, *strong* emphasis
and _underlining_ where widely accepted waaayyyy before any
newsreaders were written to treat them specially, so it's very clearly
an invalid point. If it broke up English so much, nobody would've
started using it in the first place.

Again, if you don't like it, reconfigure your newsreader. It may not
support such a reconfiguration, but if that's the case, I consider
that a mildly broken implementation. Everyone should have the right to
view unaltered, verbatim text.

And /you/, as a newcomer, certainly have no place in correcting the
format or style of message posting of an established regular.

-Micah

[Jordan Abel]

On 2006-02-27, Micah Cowan <mi***@cowan.name> wrote:

"Richard G. Riley" <rg****@gmail.com> writes:

On 2006-02-27, Vladimir S. Oka <no****@btopenworld.com> wrote:

> fr*******@yahoo.com wrote:
>

> Silly phonetic abbreviations can be /very/ hard for non-native English
> speakers to decode. I'm sure you do have some consideration (if not
> respect) for them, don't you? Otherwise: Hau vud ju lajk if aj vrote in
> vot aj konsider tu be fonetik ingli??
>
> Even for native or fluent English speakers they require extra effort to
> decode (unless they learned it from age 3, I guess).
>
> Also, /especially/ people who /really/ understand C (C++ is
> off-topic,

In many circles constant /hiliting/ is seen as obnoxious and
boring. It lights my newsreader like a beacon and for those that don't
support it, it breaks up the English. Please refrain from doing it so
frequently. It is really, really nasty.

He did no hiliting whatsoever. Any hiliting done is solely from your
newsreader. If you don't like it, see if you can turn it off.

As to the comment about it's handling in newsreaders that "don't
support it": the conventions for denoting /italics/, *strong* emphasis
and _underlining_ where widely accepted waaayyyy before any
newsreaders were written to treat them specially, so it's very clearly
an invalid point. If it broke up English so much, nobody would've
started using it in the first place.

Again, if you don't like it, reconfigure your newsreader. It may not
support such a reconfiguration, but if that's the case, I consider
that a mildly broken implementation. Everyone should have the right to
view unaltered, verbatim text.

And /you/, as a newcomer, certainly have no place in correcting the
format or style of message posting of an established regular.

I generally consider /this/ to denote a regular expression, and _this_
is italics.

[Richard G. Riley]

On 2006-02-27, Micah Cowan <mi***@cowan.name> wrote:

"Richard G. Riley" <rg****@gmail.com> writes:

On 2006-02-27, Vladimir S. Oka <no****@btopenworld.com> wrote:

> fr*******@yahoo.com wrote:
>

> Silly phonetic abbreviations can be /very/ hard for non-native English
> speakers to decode. I'm sure you do have some consideration (if not
> respect) for them, don't you? Otherwise: Hau vud ju lajk if aj vrote in
> vot aj konsider tu be fonetik ingli??
>
> Even for native or fluent English speakers they require extra effort to
> decode (unless they learned it from age 3, I guess).
>
> Also, /especially/ people who /really/ understand C (C++ is
> off-topic,

In many circles constant /hiliting/ is seen as obnoxious and
boring. It lights my newsreader like a beacon and for those that don't
support it, it breaks up the English. Please refrain from doing it so
frequently. It is really, really nasty.

He did no hiliting whatsoever. Any hiliting done is solely from your
newsreader. If you don't like it, see if you can turn it off.

/this/ is hiliting :however you want to read it. It is not conformat
to natural reading of the English language. Think of it as annoying to
me as "u" is to others. Used in its place it has a use (not/ very
/other/ word in an vain attempt to gain the moral higer ground.
As to the comment about it's handling in newsreaders that "don't
support it": the conventions for denoting /italics/, *strong* emphasis
and _underlining_ where widely accepted waaayyyy before any
newsreaders were written to treat them specially, so it's very clearly
an invalid point. If it broke up English so much, nobody would've
started using it in the first place.
Rubbish. I dont buy that at all. Ive been reading NGs for donkey years
and Ive never seen so much smug hiliting as in this one.

Again, if you don't like it, reconfigure your newsreader. It may not
support such a reconfiguration, but if that's the case, I consider
that a mildly broken implementation. Everyone should have the right to
view unaltered, verbatim text.
Actually, you might be right there. Unfortunately its only the one
poster who insists on using it to death. Occasional hiliting is
fine. Would you not agree that hiliting 20% of your post somewhat
diminishes the /reasons/ for hiliting?

And /you/, as a newcomer, certainly have no place in correcting the
format or style of message posting of an established regular.
Oh please. My "newness" to this group is really unrelated to the
constant repeated, arrogant posts from some of the established
regulars that seem to have nothing better to do than constantly post
the same nannying corrections day in , day out. And for you to even
/hilite/ the respect I ought to give a "regular" based on their time
here is so laughable as to, well, make me laugh.

-Micah

Richard.

--
Remove evomer to reply

[Micah Cowan]

"Richard G. Riley" <rg****@gmail.com> writes:

Again, if you don't like it, reconfigure your newsreader. It may not
support such a reconfiguration, but if that's the case, I consider
that a mildly broken implementation. Everyone should have the right to
view unaltered, verbatim text.
Actually, you might be right there. Unfortunately its only the one
poster who insists on using it to death.

It is also only one poster who seems to mind it.
Occasional hiliting is
fine. Would you not agree that hiliting 20% of your post somewhat
diminishes the /reasons/ for hiliting?
Once again, it is /not/ hiliting. It's denoting
emphasis/italics. Hiliting is what your own newsreader does with it.

As to the 20% thing: if the post's content is greater than around 15
words, I'd agree with you. If it's five words, I certainly
wouldn't. And I would be very interested in a citation from you for a
specific post by Vlad that has more than 10 words, with 20% "hiliting".

And /you/, as a newcomer, certainly have no place in correcting the
format or style of message posting of an established regular.

Oh please. My "newness" to this group is really unrelated to the
constant repeated, arrogant posts from some of the established
regulars that seem to have nothing better to do than constantly post
the same nannying corrections day in , day out.

No. But it is very related to how much your opinion matters on this
newsgroup, versus how much a regular's opinion: especially given the
experience level of several of them. You can hardly expect to waltz in
here and start demanding we change the way we post, especially given
that you have obviously zero respect to our own such requests.
And for you to even
/hilite/ the respect I ought to give a "regular" based on their time
here is so laughable as to, well, make me laugh.

Ooh, how clever.

[CBFalconer]

Micah Cowan wrote:

"Richard G. Riley" <rg****@gmail.com> writes:
.... snip ...

In many circles constant /hiliting/ is seen as obnoxious and
boring. It lights my newsreader like a beacon and for those that
don't support it, it breaks up the English. Please refrain from
doing it so frequently. It is really, really nasty.

.... snip ...
Again, if you don't like it, reconfigure your newsreader. It may
not support such a reconfiguration, but if that's the case, I
consider that a mildly broken implementation. Everyone should
have the right to view unaltered, verbatim text.

And /you/, as a newcomer, certainly have no place in correcting
the format or style of message posting of an established regular.

And this is coming from someone who, if I remember aright, made
himself so obnoxious over topicality that he is plonked by a fair
number of readers. I can vouch for at least one. I am assuming
your attributions are correct.

--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
More details at: <http://cfaj.freeshell.org/google/>
Also see <http://www.safalra.com/special/googlegroupsreply/>

[free2cric]

Dear group members, gurus,

I am really sorry for writing such stuff which was against the group
regulations. Actually it was my cousine who had a problem with his code
and I asked her to post it to the group under my name. I had no idea
that this gal will fry some of the finest brains here.
Not to mention I have asked her to refrain and get her own membershio
to the group. :)
Kindly review my previous posts . I have never insulted anyone in the
past.

I hope you can understand and hope to continue to offer precious help.

Thanks,

Cric.

[Default User]

fr*******@yahoo.com wrote:

Dear group members, gurus,

I am really sorry for writing such stuff which was against the group
regulations. Actually it was my cousine who had a problem with his
code and I asked her to post it to the group under my name.

You're using Google, why would this cousin need to use your account?

Brian
--
Please quote enough of the previous message for context. To do so from
Google, click "show options" and use the Reply shown in the expanded
header.

[free2cric]

This cousine of mine is only 12 years old. Her parents dont allow her
to use internet.
Its just she came to my place and by chance the issue came, as I am not
that expert, I asked her to use my system as well as my id.

Default User wrote:

fr*******@yahoo.com wrote:

Dear group members, gurus,

I am really sorry for writing such stuff which was against the group
regulations. Actually it was my cousine who had a problem with his
code and I asked her to post it to the group under my name.

You're using Google, why would this cousin need to use your account?

Brian
--
Please quote enough of the previous message for context. To do so from
Google, click "show options" and use the Reply shown in the expanded
header.