main()
{
 int n,row=1,col=40,i=0,j,k=0,count=1;
 int a[10];
 clrscr();
 i=n-1;
 printf("            WELCOME TO THE PROGRAM SIR/MADAM

<BR>);
 printf("Pyramid of how many numbers?  ");
 scanf("%d",&n);
 for (j=0;j<n;j++)
 {
  printf("Enter no.:-  ");
  scanf("%d",&a[j]);
 }
 clrscr();
 for (row=n;row>=1;row--)
 {
  k=0;
  k=40-(4*(row-1));
  i=row-1;
  for (col=40;col>=k;col=(col-4))
  {
   gotoxy(col,row);
   printf("%d",a[i]);
   --i;
  }
 }

 for (count=n;count>=1;count--)
 {
  k=0;
  k=40+(4*(count-1));
  i=count-1;
  for (col=40;col<=k;col=(col+4))
  {
   gotoxy(col,count);
   printf("%d",a[i]);
   --i;
  }
 }
 getch();
}

 

TRAPS:  This is another question that pits two values, in this case loyalty and honesty,  against one another.

BEST ANSWER:  Remember the  rule stated earlier:  In any conflict between values,  always choose integrity.

Example:  I  believe that when evaluating anything, it's important to emphasize the positive. What do I like about this idea?"

"Then, if you have reservations, I certainly want to point them out, as specifically, objectively and factually as I can. "

"After all, the most important thing I owe my boss is honesty.  If he can't count on me for that, then everything else I may do or say could be questionable in his eyes." Not sure about that one.

"Of course, if he overrules me and says, 'no, let's do it my way,' then I owe  him my full and enthusiastic support to make it work as best it can."

 

The concept of overloading in PL/SQL relates to the idea that you can define procedures and functions with the same name. PL/SQL does not look only at the referenced name, however, to resolve a procedure or function call. The count and data types of formal parameters are also considered.

PL/SQL also attempts to resolve any procedure or function calls in locally defined packages before looking at globally defined packages or internal functions. To further ensure calling the proper procedure, you can use the dot notation. Prefacing a procedure or function name with the package

In situations like, where the copy on write bit of a page is set and that page is shared by more than one process, the Kernel allocates new page and copies the content to the new page and the other processes retain their references to the old page. After copying the Kernel updates the page table entry with the new page number. Then Kernel decrements the reference count of the old pfdata table entry.

In cases like, where the copy on write bit is set and no processes are sharing the page, the Kernel allows the physical page to be reused by the processes. By doing so, it clears the copy on write bit and disassociates the page from its disk copy (if one exists), because other process may share the disk copy. Then it removes the pfdata table entry from the page-queue as the new copy of the virtual page is not on the swap device. It decrements the swap-use count for the page and if count drops to 0, frees the swap space.