<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>EmbLogic &#187; saritadalal1</title>
	<atom:link href="https://www.emblogic.com/blog/author/saritadalal1/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.emblogic.com/blog</link>
	<description>Embedded System and ARM Training</description>
	<lastBuildDate>Tue, 03 Mar 2020 13:00:06 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.1</generator>
	<item>
		<title>About fork()</title>
		<link>https://www.emblogic.com/blog/05/about-fork/</link>
		<comments>https://www.emblogic.com/blog/05/about-fork/#comments</comments>
		<pubDate>Sun, 18 May 2014 16:56:09 +0000</pubDate>
		<dc:creator><![CDATA[saritadalal1]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=10142</guid>
		<description><![CDATA[Fork is an operation whereby a process creates a copy of itself. It is usually a system call, implemented in the kernel. Fork is the primary (and historically, only) method of process creation on Unix-like operation. In multitasking operating systems, &#8230; <a href="https://www.emblogic.com/blog/05/about-fork/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>Fork is an operation whereby a process creates a copy of itself. It is usually a system call, implemented in the kernel. Fork is the primary (and historically, only) method of process creation on Unix-like operation. In multitasking operating systems, processes (running programs) need a way to create new processes, e.g. to run other programs.Fork and its variants are typically the only way of doing so in Unix-like systems.<br />
For a process to start the execution of a different program, it first forks to create a copy of itself. Then, the copy, called the &#8220;child process&#8221;, calls the exec system call to overlay itself with the other program: it ceases execution of its former program in favor of the other systems.The child process has an exact copy of all the memory segments of the parent process, though if copy-on-write semantics are implemented, the physical memory need not be actually copied. Instead, virtual memory pages in both processes may refer to the same pages of physical memory until one of them writes to such a page: then it is copied. This optimization is important in the common case where fork is used in conjunction with exec to execute a new program: typically, the child process performs only a small set of actions before it ceases execution of its program in favour of the program to be started, and it requires very few, if any, of its parent&#8217;s data structures.</p>
<p>When a process calls fork, it is deemed the parent process, and the newly created process, its child. After the fork, both processes not only run the same program, but they resume execution as though both had called the system call. They can then inspect the call&#8217;s return value to determine their status, child or parent, and act accordingly.<br />
Communication<br />
The child process inherits the standard streams from its parent, along with the rest of the environment. For interprocess communication, the parent process will often create a pipe or several pipes, and then after forking the processes will close the ends of the pipes that they don&#8217;t need.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/05/about-fork/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>multiple client using pipes</title>
		<link>https://www.emblogic.com/blog/05/multiple-client-using-pipes/</link>
		<comments>https://www.emblogic.com/blog/05/multiple-client-using-pipes/#comments</comments>
		<pubDate>Sat, 17 May 2014 07:40:03 +0000</pubDate>
		<dc:creator><![CDATA[saritadalal1]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=10128</guid>
		<description><![CDATA[description: this progra is three client and three processing with pipe using &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;- revision 1.1 date: 2014/05/17 07:12:46; author: root; state: Exp; Initial revision =============================================================================]]></description>
				<content:encoded><![CDATA[<p>description:<br />
this progra is three client and three processing with pipe using<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
revision 1.1<br />
date: 2014/05/17 07:12:46;  author: root;  state: Exp;<br />
Initial revision<br />
=============================================================================</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/05/multiple-client-using-pipes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>about pipes</title>
		<link>https://www.emblogic.com/blog/05/about-pipes/</link>
		<comments>https://www.emblogic.com/blog/05/about-pipes/#comments</comments>
		<pubDate>Mon, 12 May 2014 08:05:17 +0000</pubDate>
		<dc:creator><![CDATA[saritadalal1]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=10014</guid>
		<description><![CDATA[A pipe is a mechanism for interprocess communication; data written to the pipe by one process can be read by another process. The data is handled in a first-in, first-out (FIFO) order. The pipe has no name; it is created &#8230; <a href="https://www.emblogic.com/blog/05/about-pipes/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>A pipe is a mechanism for interprocess communication; data written to the pipe by one process can be read by another process. The data is handled in a first-in, first-out (FIFO) order. The pipe has no name; it is created for one use and both ends must be inherited from the single process which created the pipe.</p>
<p>A FIFO special file is similar to a pipe, but instead of being an anonymous, temporary connection, a FIFO has a name or names like any other file. Processes open the FIFO by name in order to communicate through it.</p>
<p>A pipe or FIFO has to be open at both ends simultaneously. If you read from a pipe or FIFO file that doesn&#8217;t have any processes writing to it (perhaps because they have all closed the file, or exited), the read returns end-of-file. Writing to a pipe or FIFO that doesn&#8217;t have a reading process is treated as an error condition; it generates a SIGPIPE signal, and fails with error code EPIPE if the signal is handled or blocked.</p>
<p>Neither pipes nor FIFO special files allow file positioning. Both reading and writing operations happen sequentially; reading from the beginning of the file and writing at the end.</p>
<p>Creating a Pipe</p>
<p>The primitive for creating a pipe is the pipe function. This creates both the reading and writing ends of the pipe. It is not very useful for a single process to use a pipe to talk to itself. In typical use, a process creates a pipe just before it forks one or more child processes. The pipe is then used for communication either between the parent or child processes, or between two sibling processes.</p>
<p>The pipe function is declared in the header file `unistd.h&#8217;.Function: int pipe (int filedes[2])</p>
<p>The pipe function creates a pipe and puts the file descriptors for the reading and writing ends of the pipe (respectively) into filedes[0] and filedes[1].</p>
<p>An easy way to remember that the input end comes first is that file descriptor 0 is standard input, and file descriptor 1 is standard output.</p>
<p>If successful, pipe returns a value of 0. On failure, -1 is returned. </p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/05/about-pipes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>program to print * using while loop in shell scripting</title>
		<link>https://www.emblogic.com/blog/04/program-to-print-using-while-loop-in-shell-scripting-2/</link>
		<comments>https://www.emblogic.com/blog/04/program-to-print-using-while-loop-in-shell-scripting-2/#comments</comments>
		<pubDate>Sat, 19 Apr 2014 06:55:44 +0000</pubDate>
		<dc:creator><![CDATA[saritadalal1]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=9851</guid>
		<description><![CDATA[1 head 1.1; 2 access; 3 symbols; 4 locks 5 root:1.1; strict; 6 comment @# @; 7 8 9 1.1 10 date 2014.04.19.12.26.46; author root; state Exp; 11 branches; 12 next ; 13 14 15 desc 16 @to print * &#8230; <a href="https://www.emblogic.com/blog/04/program-to-print-using-while-loop-in-shell-scripting-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>  1 head    1.1;<br />
  2 access;<br />
  3 symbols;<br />
  4 locks<br />
  5         root:1.1; strict;<br />
  6 comment @# @;<br />
  7<br />
  8<br />
  9 1.1<br />
 10 date    2014.04.19.12.26.46;    author root;    state Exp;<br />
 11 branches;<br />
 12 next    ;<br />
 13<br />
 14<br />
 15 desc<br />
 16 @to print * using while loop in shells scripting .<br />
 17 @<br />
 18<br />
 19<br />
 20 1.1<br />
 21 log<br />
 22 @Initial revision<br />
 23 @<br />
&#8211; INSERT &#8212;                            </p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/04/program-to-print-using-while-loop-in-shell-scripting-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>C File I/O</title>
		<link>https://www.emblogic.com/blog/03/c-file-io/</link>
		<comments>https://www.emblogic.com/blog/03/c-file-io/#comments</comments>
		<pubDate>Wed, 26 Mar 2014 16:06:23 +0000</pubDate>
		<dc:creator><![CDATA[saritadalal1]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=9511</guid>
		<description><![CDATA[FILE * For C File I/O you need to use a FILE pointer, which will let the program keep track of the file being accessed. (You can think of it as the memory address of the file or the location &#8230; <a href="https://www.emblogic.com/blog/03/c-file-io/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>FILE *</p>
<p>For C File I/O you need to use a FILE pointer, which will let the program keep track of the file being accessed. (You can think of it as the memory address of the file or the location of the file). </p>
<p>For example:<br />
FILE *fp;</p>
<p>fopen</p>
<p>To open a file you need to use the fopen function, which returns a FILE pointer. Once you&#8217;ve opened a file, you can use the FILE pointer to let the compiler perform input and output functions on the file.<br />
FILE *fopen(const char *filename, const char *mode);<br />
In the filename, if you use a string literal as the argument, you need to remember to use double backslashes rather than a single backslash as you otherwise risk an escape character such as \t. Using double backslashes \\ escapes the \ key, so the string works as it is expected.</p>
<p>fopen modes</p>
<p>The allowed modes for fopen are as follows:<br />
r  &#8211; open for reading<br />
w  &#8211; open for writing (file need not exist)<br />
a  &#8211; open for appending (file need not exist)<br />
r+ &#8211; open for reading and writing, start at beginning<br />
w+ &#8211; open for reading and writing (overwrite file)<br />
a+ &#8211; open for reading and writing (append if file exists)<br />
Note that it&#8217;s possible for fopen to fail even if your program is perfectly correct: you might try to open a file specified by the user, and that file might not exist (or it might be write-protected). In those cases, fopen will return 0, the NULL pointer. </p>
<p>Here&#8217;s a simple example of using fopen:</p>
<p>FILE *fp;<br />
fp=fopen(&#8220;c:\\test.txt&#8221;, &#8220;r&#8221;);<br />
This code will open test.txt for reading in text mode. To open a file in a binary mode you must add a b to the end of the mode string; for example, &#8220;rb&#8221; (for the reading and writing modes, you can add the b either after the plus sign &#8211; &#8220;r+b&#8221; &#8211; or before &#8211; &#8220;rb+&#8221;)</p>
<p>fclose</p>
<p>When you&#8217;re done working with a file, you should close it using the function<br />
int fclose(FILE *a_file);<br />
fclose returns zero if the file is closed successfully.</p>
<p>An example of fclose is<br />
fclose(fp);<br />
Reading and writing with fprintf, fscanf fputc, and fgetc</p>
<p>To work with text input and output, you use fprintf and fscanf, both of which are similar to their friends printf and scanf except that you must pass the FILE pointer as first argument. For example:<br />
FILE *fp;<br />
fp=fopen(&#8220;c:\\test.txt&#8221;, &#8220;w&#8221;);<br />
fprintf(fp, &#8220;Testing&#8230;\n&#8221;);<br />
It is also possible to read (or write) a single character at a time&#8211;this can be useful if you wish to perform character-by-character input (for instance, if you need to keep track of every piece of punctuation in a file it would make more sense to read in a single character than to read in a string at a time.) The fgetc function, which takes a file pointer, and returns an int, will let you read a single character from a file:<br />
int fgetc (FILE *fp);<br />
Notice that fgetc returns an int. What this actually means is that when it reads a normal character in the file, it will return a value suitable for storing in an unsigned char (basically, a number in the range 0 to 255). On the other hand, when you&#8217;re at the very end of the file, you can&#8217;t get a character value&#8211;in this case, fgetc will return &#8220;EOF&#8221;, which is a constant that indicates that you&#8217;ve reached the end of the file. To see a full example using fgetc in practice, take a look at the example here. </p>
<p>The fputc function allows you to write a character at a time&#8211;you might find this useful if you wanted to copy a file character by character. It looks like this:<br />
int fputc( int c, FILE *fp );<br />
Note that the first argument should be in the range of an unsigned char so that it is a valid character. The second argument is the file to write to. On success, fputc will return the value c, and on failure, it will return EOF.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/03/c-file-io/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>about RCS</title>
		<link>https://www.emblogic.com/blog/03/about-rcs-2/</link>
		<comments>https://www.emblogic.com/blog/03/about-rcs-2/#comments</comments>
		<pubDate>Tue, 25 Mar 2014 15:46:40 +0000</pubDate>
		<dc:creator><![CDATA[saritadalal1]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=9452</guid>
		<description><![CDATA[RCS (revision control system) is a project management tool. RCS uses a number of commands to manage source file. It works by tracking source file as its changed by maintaining a single file with list of changes in sufficient detail &#8230; <a href="https://www.emblogic.com/blog/03/about-rcs-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>RCS (revision control system) is a project management tool. RCS uses a number of commands to manage source file. It works by tracking source file as its changed by maintaining a single file with list of changes in sufficient detail to recreate the previous version. It also allows you to store comment with every change , which can be very useful to look back in the history of changes that has made to the files. To RCS a file following commands are used.</p>
<p>1.   rcs -i filename</p>
<p>this creates a rcs file with name filenamec,v.</p>
<p>2. ci filename</p>
<p>3 . co -l filename</p>
<p>this locks the previous version of file and allow you to do further changes into it.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/03/about-rcs-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>create linklist and display the data</title>
		<link>https://www.emblogic.com/blog/03/create-linklist-and-display-the-data-2/</link>
		<comments>https://www.emblogic.com/blog/03/create-linklist-and-display-the-data-2/#comments</comments>
		<pubDate>Tue, 25 Mar 2014 07:02:24 +0000</pubDate>
		<dc:creator><![CDATA[saritadalal1]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=9330</guid>
		<description><![CDATA[head 1.1; access; symbols; locks root:1.1; strict; comment @ * @; 1.1 date 2014.03.23.22.24.26; author root; state Exp; branches; next ; desc @create linklist . @ 1.1 log @Initial revision @ text @#include #include #include struct node { int roll; &#8230; <a href="https://www.emblogic.com/blog/03/create-linklist-and-display-the-data-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>head	1.1;<br />
access;<br />
symbols;<br />
locks<br />
	root:1.1; strict;<br />
comment	@ * @;</p>
<p>1.1<br />
date	2014.03.23.22.24.26;	author root;	state Exp;<br />
branches;<br />
next	;</p>
<p>desc<br />
@create linklist .<br />
@</p>
<p>1.1<br />
log<br />
@Initial revision<br />
@<br />
text<br />
@#include<br />
#include<br />
#include<br />
struct node<br />
{<br />
    int roll;<br />
    char name[20];<br />
    struct node *next;<br />
};<br />
void creat_node(struct node * temp)<br />
{<br />
    struct node *start;<br />
    temp-&gt;next=malloc(sizeof(struct node));<br />
    temp=temp-&gt;next;<br />
    printf(&#8220;\nentrer the roll&#8221;);<br />
    scanf(&#8220;%d&#8221;,&amp;temp-&gt;roll);<br />
    printf(&#8220;enter the name \n&#8221;);<br />
    scanf(&#8220;%s&#8221;,temp-&gt;name);<br />
    temp-&gt;next=NULL;</p>
<p>}<br />
void display_node(struct node *temp)<br />
{<br />
    while(temp!=NULL)<br />
    {<br />
        printf(&#8220;roll is %d\n&#8221;,temp-&gt;roll);<br />
        printf(&#8220;name is %s\n&#8221;,temp-&gt;name);<br />
        temp=temp-&gt;next;<br />
    }<br />
}<br />
int main()<br />
{<br />
    int i,n;</p>
<p>    struct node *start,*temp;<br />
    start=malloc(sizeof(struct node));<br />
    temp=start;<br />
    printf(&#8220;\nentrer the roll&#8221;);<br />
    scanf(&#8220;%d&#8221;,&amp;temp-&gt;roll);<br />
    printf(&#8220;enter the name \n&#8221;);<br />
    scanf(&#8220;%s&#8221;,temp-&gt;name);<br />
    printf(&#8220;enter the number of no. of node\n&#8221;);<br />
    scanf(&#8220;%d&#8221;,&amp;n);<br />
    temp-&gt;next=NULL;<br />
    creat_node(temp);</p>
<p>        for(i=0;inext;<br />
        }</p>
<p>    display_node(start);<br />
    {<br />
        display_node(start);<br />
    }</p>
<p>}<br />
@</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/03/create-linklist-and-display-the-data-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>enter a string and compress it with the help of masterarray</title>
		<link>https://www.emblogic.com/blog/03/enter-a-string-and-compress-it-with-the-help-of-masterarray/</link>
		<comments>https://www.emblogic.com/blog/03/enter-a-string-and-compress-it-with-the-help-of-masterarray/#comments</comments>
		<pubDate>Tue, 25 Mar 2014 06:14:34 +0000</pubDate>
		<dc:creator><![CDATA[saritadalal1]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=9320</guid>
		<description><![CDATA[head 1.1; access; symbols; locks; strict; comment @ * @; 1.1 date 2014.03.23.21.53.35; author root; state Exp; branches; next ; desc @master array with compression @ 1.1 log @Initial revision @ text @#include #include #include int main() { int i=0,j,len,maslen=1,fd,ret; &#8230; <a href="https://www.emblogic.com/blog/03/enter-a-string-and-compress-it-with-the-help-of-masterarray/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>head	1.1;<br />
access;<br />
symbols;<br />
locks; strict;<br />
comment	@ * @;</p>
<p>1.1<br />
date	2014.03.23.21.53.35;	author root;	state Exp;<br />
branches;<br />
next	;</p>
<p>desc<br />
@master array with compression<br />
@</p>
<p>1.1<br />
log<br />
@Initial revision<br />
@<br />
text<br />
@#include<br />
#include<br />
#include<br />
int main()<br />
{<br />
int i=0,j,len,maslen=1,fd,ret;<br />
char arr[100]={0};<br />
char masterarr[25]={0};<br />
fd=open(&#8220;add.c&#8221;,O_RDONLY);<br />
if(fd0;i++)<br />
{<br />
 ret=read(fd,&amp;arr[i],1);<br />
 printf(&#8220;\nret=%d,data is %c\n&#8221;,ret,arr[i]);<br />
}</p>
<p>len=strlen(arr);<br />
unsigned int ch1,ch2,comp,fd1;<br />
for(i=0;i&lt;len;i++)<br />
{<br />
for(j=0;j&lt;maslen;j++)<br />
{<br />
if(j+1==maslen)<br />
{<br />
masterarr[j]=arr[i];<br />
maslen++;<br />
break;<br />
}<br />
else<br />
{<br />
if(masterarr[j]==arr[i])<br />
break;<br />
}<br />
}<br />
}<br />
printf(&quot;masterarr=%s\n&quot;,masterarr);<br />
fd1=open(&quot;compress&quot;,O_CREAT|O_RDWR,777);<br />
if(fd&lt;0)<br />
{<br />
perror(&quot;open&quot;);<br />
goto OUT;<br />
}</p>
<p>for(i=0;i&lt;len;i++)<br />
{<br />
 for(j=0;j&lt;maslen;j++)<br />
{<br />
  if(masterarr[j]==arr[i])<br />
{<br />
 ch1=j;<br />
break;<br />
}<br />
}<br />
i++;<br />
for(j=0;j&lt;maslen;j++)<br />
{<br />
  if(masterarr[j]==arr[i])<br />
{<br />
  ch2=j;<br />
break;<br />
}<br />
}<br />
printf(&quot;value in ch1 %d\n and ch2 %d\n&quot;,ch1,ch2);</p>
<p>ch2=ch2&lt;&lt;4;<br />
comp=ch1|ch2;<br />
printf(&quot;comp=%d&quot;,comp);<br />
write(fd1,&amp;comp,1);<br />
}<br />
return 0;<br />
OUT:<br />
return-1;<br />
}</p>
<p>@</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/03/enter-a-string-and-compress-it-with-the-help-of-masterarray/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>a program that counts the no. of element that are nonzero and stop when zero is found</title>
		<link>https://www.emblogic.com/blog/03/a-program-that-counts-the-no-of-element-that-are-nonzero-and-stop-when-zero-is-found/</link>
		<comments>https://www.emblogic.com/blog/03/a-program-that-counts-the-no-of-element-that-are-nonzero-and-stop-when-zero-is-found/#comments</comments>
		<pubDate>Tue, 25 Mar 2014 06:13:54 +0000</pubDate>
		<dc:creator><![CDATA[saritadalal1]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=9185</guid>
		<description><![CDATA[1 head 1.1; 2 access; 3 symbols; 4 locks 5 root:1.1; strict; 6 comment @ * @; 7 8 9 1.1 10 date 2014.03.21.01.03.45; author root; state Exp; 11 branches; 12 next ; 13 14 15 desc 16 @counts the &#8230; <a href="https://www.emblogic.com/blog/03/a-program-that-counts-the-no-of-element-that-are-nonzero-and-stop-when-zero-is-found/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>  1 head    1.1;<br />
  2 access;<br />
  3 symbols;<br />
  4 locks<br />
  5     root:1.1; strict;<br />
  6 comment @ * @;<br />
  7<br />
  8<br />
  9 1.1<br />
 10 date    2014.03.21.01.03.45;    author root;    state Exp;<br />
 11 branches;<br />
 12 next    ;<br />
 13<br />
 14<br />
 15 desc<br />
 16 @counts the nonzero element if zero is enter then break<br />
 17 @<br />
 18<br />
 19<br />
 20 1.1<br />
 21 log<br />
 22 @Initial revision<br />
 23 @<br />
 24 text</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/03/a-program-that-counts-the-no-of-element-that-are-nonzero-and-stop-when-zero-is-found/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>pointer program</title>
		<link>https://www.emblogic.com/blog/03/pointer-program/</link>
		<comments>https://www.emblogic.com/blog/03/pointer-program/#comments</comments>
		<pubDate>Thu, 20 Mar 2014 07:51:06 +0000</pubDate>
		<dc:creator><![CDATA[saritadalal1]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=9168</guid>
		<description><![CDATA[head    1.1; access; symbols; locks; strict; comment    @ * @; 1.1 date    2014.03.20.07.44.20;    author emblogic;    state Exp; branches; next    ; desc @this is program of pointer @ 1.1 log @Initial revision @ text @]]></description>
				<content:encoded><![CDATA[<p>head    1.1;<br />
access;<br />
symbols;<br />
locks; strict;<br />
comment    @ * @;</p>
<p>1.1<br />
date    2014.03.20.07.44.20;    author emblogic;    state Exp;<br />
branches;<br />
next    ;</p>
<p>desc<br />
@this is program of pointer<br />
@</p>
<p>1.1<br />
log<br />
@Initial revision<br />
@<br />
text</p>
<p>@</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/03/pointer-program/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
