Global var in Balance calculation

Hello everyone...
Anybody can help me on this question, please?
i´ve this code in my application:
>
/*for Card creation*/
typedef struct card
{
etc,etc
} Card;
typedef Card *PtrCrt;
>
/*For trans creation*/
typedef struct trans
{
etc,etc
} Trans;
typedef Trans *PtrTrans;
>
I need to calculate the Balance of every card and how put this
verification in one function?!

Hello everyone...
Anybody can help me on this question, please?
i´ve this code in my application:
>
/*for Card creation*/
typedef struct card
{
etc,etc
} Card;
typedef Card *PtrCrt;
>
/*For trans creation*/
typedef struct trans
{
etc,etc
} Trans;
typedef Trans *PtrTrans;
>
I need to calculate the Balance of every card and how put this verification
in one function?!
>
>

Maria Mela wrote:>
Please be more specific. What is the balance of a card? What do you
need to verify? How are you representing the aggregation of cards?
As an array? A singly-linked list? Many singly-linked lists?
>
P.S.
>
http://www.nls.net/mp/413/sea.ZIP
>
Self-expanding arrays. (This is the code your college professor
warned you about.) :) :) :)

>
Thks for your help... But to be more specific here´s one part of my code...
>
#include <stdio.h>
#include <stdlib.h>
#include <conio.h>
#include <alloc.h>
#include <string.h>

P.S.
>
http://www.nls.net/mp/413/sea.ZIP
>
Self-expanding arrays. (This is the code your college professor
warned you about.) :) :) :)

Maria Mela wrote:

The above code is off-topic here, since conio.h and alloc.h are
non-standard.

Thks for your help... But to be more specific here´s one part of my code...
>
#include <stdio.h>
#include <stdlib.h>
#include <conio.h>
#include <alloc.h>
#include <string.h>
>
typedef enum observations
{
Item1=1,Item2,Item3,Item4,Item5
>
}Observations;
>
>
typedef enum trans_type
{
CRG=1, DBT,TRF
>
}Trans_type;
>
typedef enum utente
{
Student=1, Functionary ,Professor
>
}Utente;
>
typedef struct data
{
int day, month, year;
>
}Data;
>
>
typedef struct card
{
int num_card;
char name[255];
Utente utente;
Data data;
float balance;
char morada[60];
struct card *next;
>
} Card;
>
typedef Card *PtrCrt;
>
typedef struct transaccions
{
int codigo;
char nome[60];
Data data;
Trans_tipo trans_tipo;
float montante,crg;
Observacoes observacoes;
char local_treinos[60];
char nome_treinador[60];
struct trans *next;
PtrCrt p_cartao;
>
} Trans;
>
typedef Trans *PtrTrans;
/*------------------------Functions------------------------*/
>
void Insert_Card (PtrCrt *lista);
void Change_Card (PtrCrt *lista);
void Remove_Card (PtrCrt *lista);
void View_Cards (PtrCrt *lista);
void Delet_Cards (PtrCrt *lista);
int View_if_Cards (PtrCrt *lista, int cod, int ver);
>
void Insert_Trans (PtrTrans *lista);
void Remove_Trans (PtrTrans *lista);
void View_Trans (PtrTrans *lista);
void Delet_Trans (PtrTrans *lista);
int View_if_Trans (PtrTrans *lista, int cod, int ver);
>
>
void Error (char *msg);
PtrCrt Adress_Card (PtrCrt *lista, int cod);
PtrTrans Adress_Trans (PtrTrans *lista, int cod);
>
void View_Cards_Assoc (PtrCrt *lista);
void View_Card_Trans (PtrTrans *lista);
void Menu_Cards (void);
void Menu_Transaccions (void);
>
void Menu_Listall (void);
I need to calculate the Balance of every card in all new transaccions and
how put this verification
in one function?!
It´s better create one more strcut for movements (transaccions) cards?
I´m confused...
>
>
"Jeff Mullen" <413@nls.netescreveu na mensagem
news:a3da$45b46c27$49d77f6$12003@ALLTEL.NET...>
>

Jeff Mullen wrote, On 22/01/07 07:47:
>
<snip>
>>
Extracts from the code in the archive above...
>
from sea.h:
>
| #ifndef _SEA_H_
|
| #define _SEA_H_
>
Names starting with an underscore followed by an upper case letter are
reserved for use by the implementation. Don't do that.
>
from sea.c:
| else if ((ST_sea = malloc(sizeof(SEA))) == NULL)
>
Better to use:
else if ((ST_sea = malloc(sizeof *ST_sea))) == NULL)
Then you do not have to worry about getting the type correct. Very
useful if the type ever gets changed.
>
| {
| ST_sea = NULL;
| } /* if */
>
Isn't assigning NULL to ST_sea a bit pointless when you have just found
that it is equal to NULL? This smells like it has not been properly
thought out to me.
>
| if ((ST_sea->V_items = realloc(ST_sea->V_items,
ST_sea->i_num_alloc
| * ST_sea->i_item_size)) == NULL)
>
If realloc fails here you have just lost your pointer to the old, still
valid memory. You should always assign the result of realloc to a
temporary variable for testing and then, only if realloc succeeded
overwrite your old pointer.
>
Also you use something called WITHIN the definition of which is not
provided. Possibly it is defined in friendly.h, but you don't provide
that in the ZIP you provide that in the ZIP you pointed people at.
>
I've not looked any further because it currently is not in a compilable
state.

As a matter of internet etiquette, you should have sent me a private
email about this--not because the message might air some "dirty
laundry" of mine (I don't care about that if it improves the code),
but because, as I am rather busy, the message on a usenet list might
expire before I can get back to it.

You should also consider asking people whether they would like
their code reviewed when they do not explicitly request this
service.

Flash Gordon wrote:

>
Thank you for looking my code over. I hope that all the people
whom you provide with unsolicited reviews will be as forthright,
and in as much a position to make changes regarding your constructive
criticism, as I am.
>
As a matter of internet etiquette, you should have sent me a private
email about this--not because the message might air some "dirty
laundry" of mine (I don't care about that if it improves the code),
but because, as I am rather busy, the message on a usenet list might
expire before I can get back to it. Thankfully, that was not the
case this time. You should also consider asking people whether
they would like their code reviewed when they do not explicitly
request this service. As I pointed out, I appreciate your efforts,
but you should be more sensitive to the possibility of other points
of view.

Thank you for looking my code over. I hope that all the people
whom you provide with unsolicited reviews will be as forthright,
and in as much a position to make changes regarding your constructive
criticism, as I am.
>
As a matter of internet etiquette, you should have sent me a private
email about this

>As a matter of internet etiquette, you should have sent me a private
>email about this--

>because, as I am rather busy, the message on a usenet list might
>expire before I can get back to it.

>case this time. You should also consider asking people whether
>they would like their code reviewed when they do not explicitly
>request this service.

Jeff Mullen <413@nls.netwrites:

[snip]

If you don't want your code publicly reviewed, I suggest not making it
publicly available. If you don't want it reviewed in this newsgroup,
don't post a link to it in this newgroup. The review was as much for
the benefit of other readers who saw the link as it was for you.