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);

}

[Micah Cowan]

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

On 2006-02-27, Vladimir S. Oka <no****@btopenw orld.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.na me> wrote:

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

On 2006-02-27, Vladimir S. Oka <no****@btopenw orld.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.na me> wrote:

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

On 2006-02-27, Vladimir S. Oka <no****@btopenw orld.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.c om> 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.c om> 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.c om, 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/googlegroupsrep ly/>

[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.