dev-cpp-users Mailing List for Dev-C++ (Page 738)

> -----Original Message-----
> From: dev...@li...
> [mailto:dev...@li...]On Behalf Of James
> Gordon
> Sent: Friday, January 05, 2001 10:40 AM
> To: 'dev...@li...'
> Subject: RE: [Dev-C++] The new C99 Standard
>
>
> Taking the example
>
> drawline((struct point) {.y=2, .x=1}, (struct point) {.x=3, .y=1});
>
> Is easier than
>
> {
> struct point mypoint1, mypoint2;
> mypoint1.y = 2;
> mypoint1.x = 1;
> mypoint2.y = 3;
> mypoint2.x = 1;
> drawline(mypoint1, mypoint2);
> ... 100's of lines later
> } <- Now mypoint1 & 2 are destroyed.
>

Do you find these:

struct {int a[2], b}; x[]={[0].a = {1}, [1].a[0] = 2};


 struct s { int n; double d[]; };
------------------------------------

 struct s *s1=malloc(sizeof(struct s)+64); //64 is for the d[]
 s1->d[0]=...

as badly needed too?

> Why does long long corrupt existing code?

:))
Because the previous standard assumed long as the biggest integer and
programs were written with that in mind. Obviously we have different
opinions on the matter but is long long the biggest integer? Do not forget
that more integers were introduced (breaking further the compatibility):

http://www.freshsources.com/dev/Forums/C99/sld014.htm (please take a look at
it)

I guess that the biggest integer is intmax_t.


>
> I'm sure that the committee try only to make changes which doesn't break
> existing code, as does the C++ committee not change things that
> might break
> existing C code when using a compliant C++ compiler.
>
> As to the bool thing. Well people have been doing that sort of thing for
> years. I started by using #define's and then moved onto enum's
> later on. So
> they've move that code into the standard, big deal. Old code can still use
> the hand crafted stuff. New code can make use of the new header.
>
> as to
> >b) "New" C is bloated with unuseful new complementary features much like
> the pascal things write, writeln...
>
> Well they probably said that to the C89 standard. 'It's just code bloat',
> etc.
> Isn't that what a standard is for, to evolve and take things that
> everybody
> has had to do by hand and incorporate into the standard to make things
> easier?
>
> They must have a hard job to improve the standard but still not break
> existing code if at all possible. Not the sort of job I'd like to do.
>
> Regards,
>
> James.

As i said, we simply disagree. :)


Ioannis

Thanks!!

> -----Original Message-----
> From:	Ioannis Vranos [SMTP:no...@ya...]
> Sent:	Friday, January 05, 2001 9:49 AM
> To:	dev...@li...
> Subject:	RE: [Dev-C++] Hexadecimal Numbers
> 
> A number is stored and seen by a computer in binary format. So for example
> 4
> is stored as
> 100 . When you want to see the number in decimal format you use
> printf("%d",
> 4);
>  Now there are more number systems than decimal format. Decimal format has
> its number base 0-9.
> Binary format has its number base 0-1. Hexadecimal format (your Hex) has
> its
> number base consisted of 16 numbers (0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F). So
> our 4 (in decimal format) is 4 in Hex too.
> 10 is A in Hex.
>  As i said your computer stores all the numbers in binary format. So
> assigning a variable x as:
> 
> x=11;
> 
> or x=0xb; (0x indicates hexadecimal format)
> 
> is the same for your computer. To see the hexadecimal value without the 0x
> of an integer in C use
> 
> printf("%x", variable);
> 
> e.g. printf("%x", 11);
> 
> 
> %X makes the values appear in capital letterrs.
> 
> 
> Ioannis
> 
> > -----Original Message-----
> > From: dev...@li...
> > [mailto:dev...@li...]On Behalf Of Caroline
> > Tully
> > Sent: Friday, January 05, 2001 11:12 AM
> > To: 'dev...@li...'
> > Subject: [Dev-C++] Hexadecimal Numbers
> > Importance: High
> >
> >
> > Help!!
> > I'm working my way through a ' Teach yourself C ' book and have reached
> a
> > Chapter about Hex.
> > I wondered if anyone knew where I could get further information on Hex,
> as
> > my book doesnt go into very much detail and it's making my head hurt!!!
> > Please email me at ' car...@no... '  with any links.
> > Cheers!
> > Caroline
> >
> > _______________________________________________
> > Dev-cpp-users mailing list
> > Dev...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dev-cpp-users
> >
> 
> 
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> http://lists.sourceforge.net/mailman/listinfo/dev-cpp-users
> 
> _____________________________________________________________________
> This message has been checked for all known viruses by Star Internet
> delivered
> through the MessageLabs Virus Control Centre. For further information
> visit
> http://www.star.net.uk/stats.asp

A number is stored and seen by a computer in binary format. So for example 4
is stored as
100 . When you want to see the number in decimal format you use printf("%d",
4);
 Now there are more number systems than decimal format. Decimal format has
its number base 0-9.
Binary format has its number base 0-1. Hexadecimal format (your Hex) has its
number base consisted of 16 numbers (0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F). So
our 4 (in decimal format) is 4 in Hex too.
10 is A in Hex.
 As i said your computer stores all the numbers in binary format. So
assigning a variable x as:

x=11;

or x=0xb; (0x indicates hexadecimal format)

is the same for your computer. To see the hexadecimal value without the 0x
of an integer in C use

printf("%x", variable);

e.g. printf("%x", 11);


%X makes the values appear in capital letterrs.


Ioannis

> -----Original Message-----
> From: dev...@li...
> [mailto:dev...@li...]On Behalf Of Caroline
> Tully
> Sent: Friday, January 05, 2001 11:12 AM
> To: 'dev...@li...'
> Subject: [Dev-C++] Hexadecimal Numbers
> Importance: High
>
>
> Help!!
> I'm working my way through a ' Teach yourself C ' book and have reached a
> Chapter about Hex.
> I wondered if anyone knew where I could get further information on Hex, as
> my book doesnt go into very much detail and it's making my head hurt!!!
> Please email me at ' car...@no... '  with any links.
> Cheers!
> Caroline
>
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> http://lists.sourceforge.net/mailman/listinfo/dev-cpp-users
>

Thanks, Its a headache because I'm a complete novice on computers and i've
just starting trying to teach myself C. 

> -----Original Message-----
> From:	James Gordon [SMTP:Jam...@Cl...]
> Sent:	Friday, January 05, 2001 9:23 AM
> To:	'dev...@li...'
> Subject:	RE: [Dev-C++] Hexadecimal Numbers
> 
> What is the actual headache?
> 
> Hex is only a way of displaying/storing numbers.
> Humans use base 10 and so the numbers repeat at 10.
> e.g. 1,2,3,4,5,6,7,8,9,10,11,12...
> Hex is base 16 so the numbers repeat after 16 numbers.
> e.g.
> 1,2,3,4,5,6,7,8,9,a,b,c,d,e,f,10,11,12,13,14,15,16,17,18,19,1a,1b,1c,1d,1e
> ,1
> f,20...
> 
> Regards,
> 
> James.
> 
> 
> -----Original Message-----
> From: Caroline Tully [mailto:Car...@no...]
> Sent: Friday, January 05, 2001 9:12 AM
> To: 'dev...@li...'
> Subject: [Dev-C++] Hexadecimal Numbers
> Importance: High
> 
> 
> Help!! 
> I'm working my way through a ' Teach yourself C ' book and have reached a
> Chapter about Hex. 
> I wondered if anyone knew where I could get further information on Hex, as
> my book doesnt go into very much detail and it's making my head hurt!!!
> Please email me at ' car...@no... '  with any links.
> Cheers!
> Caroline
> 
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> http://lists.sourceforge.net/mailman/listinfo/dev-cpp-users
> 
> 
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
> This electronic message and any attachment is intended to be 
> read by the named addressee(s) only. 
> Any other recipient should be aware that its contents may be 
> legally privileged and/or confidential and that its use, 
> disclosure, copying or distribution may be unlawful. 
> Unless you are a named addressee, please delete this message 
> 
> Whilst C. & J. Clark International Limited has taken steps 
> to prevent the transmission of computer viruses with electronic mail, 
> responsibility for screening incoming messages and the risk of such 
> transmission and its consequences lies with the recipient. 
> 
> C. & J. Clark International Limited 
> Registered in England and Wales 
> Company No. 141015 
> Registered Office: 40 High Street, Street, Somerset BA16 0YA 
> Telephone: +44 (0) 1458 443131 
> Fax: +44 (0) 1458 447547 
> 
> 
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> http://lists.sourceforge.net/mailman/listinfo/dev-cpp-users
> 
> _____________________________________________________________________
> This message has been checked for all known viruses by Star Internet
> delivered
> through the MessageLabs Virus Control Centre. For further information
> visit
> http://www.star.net.uk/stats.asp

What is the actual headache?

Hex is only a way of displaying/storing numbers.
Humans use base 10 and so the numbers repeat at 10.
e.g. 1,2,3,4,5,6,7,8,9,10,11,12...
Hex is base 16 so the numbers repeat after 16 numbers.
e.g.
1,2,3,4,5,6,7,8,9,a,b,c,d,e,f,10,11,12,13,14,15,16,17,18,19,1a,1b,1c,1d,1e,1
f,20...

Regards,

James.


-----Original Message-----
From: Caroline Tully [mailto:Car...@no...]
Sent: Friday, January 05, 2001 9:12 AM
To: 'dev...@li...'
Subject: [Dev-C++] Hexadecimal Numbers
Importance: High


Help!! 
I'm working my way through a ' Teach yourself C ' book and have reached a
Chapter about Hex. 
I wondered if anyone knew where I could get further information on Hex, as
my book doesnt go into very much detail and it's making my head hurt!!!
Please email me at ' car...@no... '  with any links.
Cheers!
Caroline

_______________________________________________
Dev-cpp-users mailing list
Dev...@li...
http://lists.sourceforge.net/mailman/listinfo/dev-cpp-users


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
This electronic message and any attachment is intended to be 
read by the named addressee(s) only. 
Any other recipient should be aware that its contents may be 
legally privileged and/or confidential and that its use, 
disclosure, copying or distribution may be unlawful. 
Unless you are a named addressee, please delete this message 

Whilst C. & J. Clark International Limited has taken steps 
to prevent the transmission of computer viruses with electronic mail, 
responsibility for screening incoming messages and the risk of such 
transmission and its consequences lies with the recipient. 

C. & J. Clark International Limited 
Registered in England and Wales 
Company No. 141015 
Registered Office: 40 High Street, Street, Somerset BA16 0YA 
Telephone: +44 (0) 1458 443131 
Fax: +44 (0) 1458 447547 

Help!! 
I'm working my way through a ' Teach yourself C ' book and have reached a
Chapter about Hex. 
I wondered if anyone knew where I could get further information on Hex, as
my book doesnt go into very much detail and it's making my head hurt!!!
Please email me at ' car...@no... '  with any links.
Cheers!
Caroline

A DLL is the same as a shard library (normally .so) in Unix.
It allows a set of code to be shared by a number of executables without it
being linked to the executable file. Thus the DLL can be changed and the
executable can use the new (improved) code without relinking it. It also
allows one or more executables to share the DLL code thus cutting down on
memory usage. The variables are not shared only the code.
 
Regards, 

James. 

 

-----Original Message-----
From: softnasolutions-ltd.fsbusiness.co.uk
[mailto:so...@so...]
Sent: Thursday, January 04, 2001 6:47 PM
To: dev...@li...
Subject: [Dev-C++] What is a DLL file


 
Hi everyone,
Please what is a dll(dynamic link library) ?
 Why would i want to create one ? 
What is the difference between an EXE file and a DLL file ?
 
Thnx
 
Napoleon
 



* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
This electronic message and any attachment is intended to be 
read by the named addressee(s) only. 
Any other recipient should be aware that its contents may be 
legally privileged and/or confidential and that its use, 
disclosure, copying or distribution may be unlawful. 
Unless you are a named addressee, please delete this message 

Whilst C. & J. Clark International Limited has taken steps 
to prevent the transmission of computer viruses with electronic mail, 
responsibility for screening incoming messages and the risk of such 
transmission and its consequences lies with the recipient. 

C. & J. Clark International Limited 
Registered in England and Wales 
Company No. 141015 
Registered Office: 40 High Street, Street, Somerset BA16 0YA 
Telephone: +44 (0) 1458 443131 
Fax: +44 (0) 1458 447547 

Taking the example

drawline((struct point) {.y=2, .x=1}, (struct point) {.x=3, .y=1});

Is easier than

{
struct point mypoint1, mypoint2;
mypoint1.y = 2;
mypoint1.x = 1;
mypoint2.y = 3;
mypoint2.x = 1;
drawline(mypoint1, mypoint2);
... 100's of lines later
} <- Now mypoint1 & 2 are destroyed.

Why does long long corrupt existing code?

I'm sure that the committee try only to make changes which doesn't break
existing code, as does the C++ committee not change things that might break
existing C code when using a compliant C++ compiler.

As to the bool thing. Well people have been doing that sort of thing for
years. I started by using #define's and then moved onto enum's later on. So
they've move that code into the standard, big deal. Old code can still use
the hand crafted stuff. New code can make use of the new header.

as to 
>b) "New" C is bloated with unuseful new complementary features much like
the pascal things write, writeln...

Well they probably said that to the C89 standard. 'It's just code bloat',
etc.
Isn't that what a standard is for, to evolve and take things that everybody
has had to do by hand and incorporate into the standard to make things
easier?

They must have a hard job to improve the standard but still not break
existing code if at all possible. Not the sort of job I'd like to do.

Regards,

James.


-----Original Message-----
From: Ioannis Vranos [mailto:no...@ya...]
Sent: Thursday, January 04, 2001 6:59 PM
To: dev...@li...
Subject: RE: [Dev-C++] The new C99 Standard


Do you find this kind of stuff:

drawline((struct point) {.y=2, .x=1}, (struct point) {.x=3, .y=});
int a[]={[2]=3, [1]=2, [0]=1};

enum{ first, second};
const char *nm[]={[second]="second", [first]="first",};

struct {int a[2], b}; x[]={[0].a = {1}, [1].a[0] = 2};

as missing and recommended additions, that is, there was no other way of
doing this? C's power has been for years the fact that it was small, yet
versatile enough to do anything. The only useful and needed addition was
that of restricted pointers. The rest of the "improvements" are bloated
features without providing any easier way to do things already be done. long
long type corrupts compatibility with the previous standard and C++. Aside
of C++, the previous standard considered long as the bigger integral type,
and all programs written then were asssuming long as the biggest integral
type. We could live for years without bool defined in stdbool.h . I imagine
the bool improvement is something like:

stdbool.h:

enum bool{FALSE, TRUE};

what an improvement!

  All these bloated language extensions (and long long corrupting
compatibility wiith the previous C and existing C++ standards) show the
following things:

a) Most in the committee were fortran programmers or were bored to vote
negatively, or were too friendly with one another and did not want to create
bad feelings.

b) "New" C is bloated with unuseful new complementary features much like the
pascal things write, writeln...

c) Basic issues were not covered. Type safety mechanisms were not
introduced, better code management mechanisms such as C++ namespaces were
not adopted. These are better things to adopt than things from fortran.

Conclusion: No any new benefits (except of the restrict pointers and perhaps
the variable sized arrays although the second was accessible via realloc()),
and yet one has to learn a lot more things so as to be credited to say that
he knows the whole C language.

Of course this is my personal opinion which will not change facts after all.
:) Just mentioning my opinion. I think that the new standard brings much
trouble to the viability of the language.


Ioannis

> -----Original Message-----
> From: dev...@li...
> [mailto:dev...@li...]On Behalf Of James
> Gordon
> Sent: Thursday, January 04, 2001 6:06 PM
> To: 'dev...@li...'
> Subject: RE: [Dev-C++] The new C99 Standard
>
>
> I don't really see what the problem is. Most of it merely adds new
> functionality or allows things that developers want to do be done in the
> language rather than rolling your own.
>
> I don't think it breaks much, if anything.
>
> e.g. bool is only define if you include the header, which you
> would only do
> as part of an upgrade/re-write.
>
> If you can define variables as being sized at runtime than e.g. char
> ms[b+3]; than that's good, isn't it?
>
> The %ll etc. in snprintf is additional functionality, won't break existing
> code and might make new code easier to write.
>
> New types, no problem there?
>
> Elastic structures, well I could of used that years ago.
>
> Designators, seems good to me, creating temporary objects in the function
> call saves having an object on the stack for the lifetime of the function
> just to pass it to one function.
>
> iso646, again, doesn't break code merely help in the readability.
>
> Regards,
>
> James.


_______________________________________________
Dev-cpp-users mailing list
Dev...@li...
http://lists.sourceforge.net/mailman/listinfo/dev-cpp-users


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
This electronic message and any attachment is intended to be 
read by the named addressee(s) only. 
Any other recipient should be aware that its contents may be 
legally privileged and/or confidential and that its use, 
disclosure, copying or distribution may be unlawful. 
Unless you are a named addressee, please delete this message 

Whilst C. & J. Clark International Limited has taken steps 
to prevent the transmission of computer viruses with electronic mail, 
responsibility for screening incoming messages and the risk of such 
transmission and its consequences lies with the recipient. 

C. & J. Clark International Limited 
Registered in England and Wales 
Company No. 141015 
Registered Office: 40 High Street, Street, Somerset BA16 0YA 
Telephone: +44 (0) 1458 443131 
Fax: +44 (0) 1458 447547 

Most 'modern' systems support the 640x800 16bit, so most graphics libs expect it to be there.
DirectX MIGHT support lower settings, or at least convince your system that it supports that one.
:-)


Original message from: "jag"
>I've tried using allegro graphics library for c++ but have found that my
>system does n't support the graphics mode used for it (640x800 16bit high
>color mode).
>What other graphics libraries do are out there?
>Are there any standard libraries that come with devc++?
>
>
>
>_______________________________________________
>Dev-cpp-users mailing list
>Dev...@li...
>http://lists.sourceforge.net/mailman/listinfo/dev-cpp-users
>

How do I make a PUSHBUTTON respond to a key?
For example, when you click File->Open in Dev-C++ you have a window to open
the file. If you press escape, the "Cancel" button is pressed and if you
press enter, the "Open" button is pressed.

How can I make a button I create respond to a key like this?
I make the button in the resources file in a dialog box:

...
PUSHBUTTON "Cancel",-1,0,0,100,15
...

When I make an item on a menu respond to a key, it is like this:

Myaccel ACCELERATORS
{
 <key>,<ID>,VIRTKEY
}

Is there a similar thing for buttons?

Please note from my source code that I am using the Win32 API, but, if you
know of a way I can solve the problem that is different from this (and, of
course, works in Dev-C++) I would be happy to hear about it.

Thank you,
Xerchzkopfinc. Ramana Kumar (Ra...@my...)
ICQ# 93667117
To get paid for surfing the 'net please visit
https://www.alladvantage.com/joinsecure.asp?refid=jpn471&cntry=1

How do I make a PUSHBUTTON respond to a key?
For example, when you click File->Open in Dev-C++ you have a window to open
the file. If you press escape, the “Cancel” button is pressed and if you
press enter, the “Open” button is pressed.

How can I make a button I create respond to a key like this?
I make the button in the resources file in a dialog box:

…
PUSHBUTTON “Cancel”,-1,0,0,100,15
…

When I make an item on a menu respond to a key, it is like this:

Myaccel ACCELERATORS
{
 <key>,<ID>,VIRTKEY
}

Is there a similar thing for buttons?

Please note from my source code that I am using the Win32 API, but, if you
know of a way I can solve the problem that is different from this (and, of
course, works in Dev-C++) I would be happy to hear about it.

Thank you,
Xerchzkopfinc. Ramana Kumar
ICQ# 93667117
To get paid for surfing the ‘net please visit
https://www.alladvantage.com/joinsecure.asp?refid=jpn471&cntry=1

 <mailto:ra...@my...>
ICQ# 93667117
To get paid for surfing the internet, please visit AllAdvantage.com
<http://www.alladvantage.com/join.asp?refid=jpn471> .

----- Original Message -----
From: "Ioannis Vranos" <no...@ya...>
To: <dev...@li...>
Sent: Thursday, January 04, 2001 6:52 PM
Subject: RE: [Dev-C++] what is a resource? how do I create my own headers?

> > The #ifdef/#endif only works for the current compile. So, if you include
> > a header file that contains a definition in more than one translation
unit
> > (.cpp file), you will get multiple definitions of the function, which is
> > gonna
> > be flagged as an error by the linker.
>
> I agree with you, but why create many definitions in many cpp files?
Except
> of that, you can use #ifndef at definitions too (it is called "conditional
> compilation").
>  Anyway, if i remember well we were talking about definitions included in
> the header file, not external source code files (where as i said we can
use
> conditional compilation too).


I don't see where I might have hinted at having "many
definition in many .cpp files".

In C/C++ (I don't know for other languages), you can't
have more than one definition for a symbol, be it a variable,
a function or a class. This is called, IIRC, the "One Definition
Rule".

If you start putting definitions in header files, as projects grow
bigger, those header files risk being included in more than
one .cpp file, leading to multiple definitions of the functions
in the header files.

Now, I've seen tricks posted here to work around this, but
why use tricks when all you have to do is _declare_ your
functions (or classes) in a header file, and _define_ said
functions (or classes) in only one .cpp file. Then, wherever
you need that function, all you need to do is #include your
header file.

Let the linker do its job :-)

Regards,

Luc Morin

I've tried using allegro graphics library for c++ but have found that my
system does n't support the graphics mode used for it (640x800 16bit high
color mode).
What other graphics libraries do are out there?
Are there any standard libraries that come with devc++?

> -----Original Message-----
> From: dev...@li...
> [mailto:dev...@li...]On Behalf Of Luc Morin
> Sent: Friday, January 05, 2001 1:29 AM
> To: dev...@li...
> Subject: Re: [Dev-C++] what is a resource? how do I create my own headers?
>
> While I do agree that this will protect agaisnt multiple _inclusion_, it
> will
> NOT protect agaisnt multiple _definition_ of a function located
> in a header
> file.
>
> The #ifdef/#endif only works for the current compile. So, if you include
> a header file that contains a definition in more than one translation unit
> (.cpp file), you will get multiple definitions of the function, which is
> gonna
> be flagged as an error by the linker.

I agree with you, but why create many definitions in many cpp files? Except
of that, you can use #ifndef at definitions too (it is called "conditional
compilation").
 Anyway, if i remember well we were talking about definitions included in
the header file, not external source code files (where as i said we can use
conditional compilation too).


Friendly,
Ioannis

* Ioannis Vranos
* Programming pages: http://members.nbci.com/noicys
* Alternative URL: http://run.to/noicys

----- Original Message -----
From: "Ioannis Vranos" <no...@ya...>
To: <dev...@li...>
Sent: Thursday, January 04, 2001 10:07 AM
Subject: RE: [Dev-C++] what is a resource? how do I create my own headers?


> He can use the following notation so as to bbe protected from multiple
> includes.
>
> #ifndef PINKY&THE_BRAIN
>
> #define PINKY&THE_BRAIN
> // implementation stuff
> #endif
>
>
> Ioannis
>

While I do agree that this will protect agaisnt multiple _inclusion_, it
will
NOT protect agaisnt multiple _definition_ of a function located in a header
file.

The #ifdef/#endif only works for the current compile. So, if you include
a header file that contains a definition in more than one translation unit
(.cpp file), you will get multiple definitions of the function, which is
gonna
be flagged as an error by the linker.

Regards,

Luc Morin

Ramana et al.,

            A resource file WAS specified under Project Options, for =
some reason.  Anyway, I am no longer getting this resource error. =20

    I did get an error until I figured out that the "#include" =
statements and global constants had to be in the .cpp file, not the =
header file.  Then, since my function declarations were now in the =
header file, I had to pay attention to the order of the function =
definitions in .cpp.  After that, sucess!

        Thank you for your help,       Alan

From: "Ramana Kumar" <ra...@my...>
Subject: RE: [Dev-C++] what is a resource?  how do I create my own =
headers?
Date: Thu, 4 Jan 2001 13:16:35 +1100

A resource file is not needed for a dos project. You shouldn't be =
getting
any errors if you don't touch the resource file, but, if you do, go to
Project Options and remove the text in the resource file field, or, open =
the
resource file and edit it (delete its contents).

Yes, Dev-C++ has it.


Ioannis
  -----Original Message-----
  From: dev...@li...
[mailto:dev...@li...]On Behalf Of Frazell
Thomas
  Sent: Thursday, January 04, 2001 10:43 PM
  To: dev...@li...
  Subject: Re: [Dev-C++] Reg. Program


  Dev. C++ has it? cause it gives me an error

Dev. C++ has it? cause it gives me an error
  ----- Original Message -----=20
  From: Ioannis Vranos=20
  To: dev...@li...=20
  Sent: Thursday, January 04, 2001 2:03 PM
  Subject: RE: [Dev-C++] Reg. Program


  This is header file from the C++ standard library.


  Ioannis
    -----Original Message-----
    From: dev...@li... =
[mailto:dev...@li...]On Behalf Of Frazell =
Thomas
    Sent: Thursday, January 04, 2001 7:27 PM
    To: dev...@li...
    Subject: [Dev-C++] Reg. Program


    I got some sorce from Mr. Hoo Hang it was excelently layed out and =
with a few tweaks i could have got it to do what i needed done the =
problem was he was using a custom header it looks like if any one (or =
Mr. Hang) can send me the file with a small def. of its functions i =
would be greatful

    the file was

    #include <string>

I was able to compile Hoo Hong's code from the attachment sent, not=20
straight from a copy of the original post. The code does work on my Win98=20
system.

I find it very interesting code, and can see some uses in my job,=20
especially for fixing known problems with the registry, or doing custom=20
edits. Granted a .reg file can do the job, but this helps one learn=20
programming skills! <g> I can see how this could be easily modified for=20
custom input during program execution, in a word, cool!

I am in the playing stage of working with C/C++, since I do not have time=20
to sit down and really think all this through. I do like the working=20
examples shared on this list though, it sure helps make sense out of the=20
discussions.

Larry Hamilton

At 07:55 PM 01/03/2001 +1100, you wrote:
>I haven=92t thoroughly read all this code regarding the registry, but, if=
 Hoo
>Hong=92s code works, there may be a difference (or problem) with you system
>setup, Frazell. What OS are you using, and what does your registry look=
 like
>(in regedit) =AD compare this with Hoo Hong=92s. If the program doesn=92t=
 even
>compile, yet compiles on another system, maybe you should check all the
>settings and/or re-install Dev-C++. I saw that your hard drive is E:, I=92m
>not sure, but maybe Dev-C++ automatically sets up its default settings to a
>hard drive which is C:. Go to Options->Compiler Options and check that
>everything is all right.

This is header file from the C++ standard library.


Ioannis
  -----Original Message-----
  From: dev...@li...
[mailto:dev...@li...]On Behalf Of Frazell
Thomas
  Sent: Thursday, January 04, 2001 7:27 PM
  To: dev...@li...
  Subject: [Dev-C++] Reg. Program


  I got some sorce from Mr. Hoo Hang it was excelently layed out and with a
few tweaks i could have got it to do what i needed done the problem was he
was using a custom header it looks like if any one (or Mr. Hang) can send me
the file with a small def. of its functions i would be greatful

  the file was

  #include <string>

Do you find this kind of stuff:

drawline((struct point) {.y=2, .x=1}, (struct point) {.x=3, .y=});
int a[]={[2]=3, [1]=2, [0]=1};

enum{ first, second};
const char *nm[]={[second]="second", [first]="first",};

struct {int a[2], b}; x[]={[0].a = {1}, [1].a[0] = 2};

as missing and recommended additions, that is, there was no other way of
doing this? C's power has been for years the fact that it was small, yet
versatile enough to do anything. The only useful and needed addition was
that of restricted pointers. The rest of the "improvements" are bloated
features without providing any easier way to do things already be done. long
long type corrupts compatibility with the previous standard and C++. Aside
of C++, the previous standard considered long as the bigger integral type,
and all programs written then were asssuming long as the biggest integral
type. We could live for years without bool defined in stdbool.h . I imagine
the bool improvement is something like:

stdbool.h:

enum bool{FALSE, TRUE};

what an improvement!

  All these bloated language extensions (and long long corrupting
compatibility wiith the previous C and existing C++ standards) show the
following things:

a) Most in the committee were fortran programmers or were bored to vote
negatively, or were too friendly with one another and did not want to create
bad feelings.

b) "New" C is bloated with unuseful new complementary features much like the
pascal things write, writeln...

c) Basic issues were not covered. Type safety mechanisms were not
introduced, better code management mechanisms such as C++ namespaces were
not adopted. These are better things to adopt than things from fortran.

Conclusion: No any new benefits (except of the restrict pointers and perhaps
the variable sized arrays although the second was accessible via realloc()),
and yet one has to learn a lot more things so as to be credited to say that
he knows the whole C language.

Of course this is my personal opinion which will not change facts after all.
:) Just mentioning my opinion. I think that the new standard brings much
trouble to the viability of the language.


Ioannis

> -----Original Message-----
> From: dev...@li...
> [mailto:dev...@li...]On Behalf Of James
> Gordon
> Sent: Thursday, January 04, 2001 6:06 PM
> To: 'dev...@li...'
> Subject: RE: [Dev-C++] The new C99 Standard
>
>
> I don't really see what the problem is. Most of it merely adds new
> functionality or allows things that developers want to do be done in the
> language rather than rolling your own.
>
> I don't think it breaks much, if anything.
>
> e.g. bool is only define if you include the header, which you
> would only do
> as part of an upgrade/re-write.
>
> If you can define variables as being sized at runtime than e.g. char
> ms[b+3]; than that's good, isn't it?
>
> The %ll etc. in snprintf is additional functionality, won't break existing
> code and might make new code easier to write.
>
> New types, no problem there?
>
> Elastic structures, well I could of used that years ago.
>
> Designators, seems good to me, creating temporary objects in the function
> call saves having an object on the stack for the lifetime of the function
> just to pass it to one function.
>
> iso646, again, doesn't break code merely help in the readability.
>
> Regards,
>
> James.

Hi everyone,
Please what is a dll(dynamic link library) ?
 Why would i want to create one ?=20
What is the difference between an EXE file and a DLL file ?

Thnx

Napoleon

Hi everyone,
Please what is a dll(dynamic link library) ?
 Why would i want to create one ?=20
What is the difference between an EXE file and a DLL file ?
=20

I got some sorce from Mr. Hoo Hang it was excelently layed out and with =
a few tweaks i could have got it to do what i needed done the problem =
was he was using a custom header it looks like if any one (or Mr. Hang) =
can send me the file with a small def. of its functions i would be =
greatful

the file was

#include <string>

I don't really see what the problem is. Most of it merely adds new
functionality or allows things that developers want to do be done in the
language rather than rolling your own.

I don't think it breaks much, if anything.

e.g. bool is only define if you include the header, which you would only do
as part of an upgrade/re-write.

If you can define variables as being sized at runtime than e.g. char
ms[b+3]; than that's good, isn't it?

The %ll etc. in snprintf is additional functionality, won't break existing
code and might make new code easier to write.

New types, no problem there?

Elastic structures, well I could of used that years ago.

Designators, seems good to me, creating temporary objects in the function
call saves having an object on the stack for the lifetime of the function
just to pass it to one function.

iso646, again, doesn't break code merely help in the readability.

Regards,

James.


-----Original Message-----
From: ropbert d baugh [mailto:lon...@ju...]
Sent: Tuesday, January 02, 2001 10:44 PM
To: dev...@li...
Subject: Re: [Dev-C++] The new C99 Standard


Looks like you are right. Pile of JUNK!

lon...@ju...

On Tue, 2 Jan 2001 20:48:35 +0200 "Ioannis Vranos" <no...@ya...>
writes:
> Except of the long long type which corrupts compatibility with C89 & 
> C++,
> and the _Bool type defined only in boolean.h (not built in type) 
> which may
> or may not be stupid, there are a lot of fortran-style!!! stupid 
> additions
> which corrupt compatibility with common sense and according to my 
> opinion
> destroyed forever the language.
> 
> Examples:
> 
> 1) snprintf()
> 2) new formats for printf(). E.g. %ll for long long. We are used to 
> %$d
> stuff for signed integers, where $ the integer type, so %ll is 
> something you
> have to remember isolated.
> 
> 
> And now fasten your seabelt, "the great things" adopted by fortran:
> 
> 3) int *p=(int []) {2, 4}
> 
> It is something like a pointer pointing to an array where the first 
> 2
> elements are 2, 4. Or something like that, i do not know and i do 
> not want
> to know..
> 
> 
> 4) int (*q)[2]=(int[][2]) {{1,2}, {3,4}, {5,6}, {7, 8}};
> 
> It is something an array of 2 pointers to functions accepting an 
> int
> 2-dimensional array with default values?
> 
> 
> 5) drawline((struct point) {1, 2}, (struct point) {3, 4});
> 
> It is a function accepting two *anonymous*(!) probably variable 
> structs with
> default values?
> 
> 
> 6) drawline((struct point) {.y=2, .x=1}, (struct point) {.x=3, 
> .y=});
> 
> This creates 2 anonymous structs with those values. The structs and 
> the
> values are created in there!!
> 
> 
> 7) int a[]={[2]=3, [1]=2, [0]=1};
> 
> Translation: We create an array with the third element=3, the 
> second=2, and
> the first=1. The same we used till nowadays as int a[]={1, 2, 3};
> 
> 
> 8) enum{ first, second};
> 
> const char *nm[]={[second]="second", [first]="first",};
> 
> Translation: The second element of the array gets the value "second" 
> and the
> first the value "first".
> 
> I wonder why the last comma (,) is used but perhaps it is a variable 
> array
> or something.
> 
> 
> 9) int a[MAX]={1, 3, 5, [MAX-3]= 4, 2, 0};
> 
> The "fortan-miracles" of the new standard: We give to the first 3 
> elements
> of the array the values 1, 3, 5 and the 3 elements at the end the 
> values 4,
> 2, and 0.
> 
> 
> 10) struct {int a[2], b}; x[]={[0].a = {1}, [1].a[0] = 2};
> 
> I will try to translate this: We create an anonymous struct and then 
> an
> array of it named x, with the first element taking the values: 
> [0].a[0]=1 &
> [0].a[1]=1 both using the notation [0].a=1 , and the second elemet 
> of the
> structure array x taking the value 1 at its first only array 
> element:
> 
> [1].a[0]=2
> 
> 
> 11)
> 
> size_t fsize3(int n)
> {
>  char b[n+3]; // Variable Length (Fortran-style) Array
>  return sizeof b;
> }
> 
> int main()
> {
>  size_t size=fsize3(10); // 13
> 
>  return 0;
> }
> 
> 
> 12)
> 
>  void rowSum(int, int, int[*][*], int[*]);
> 
>          //             ^^^^^^^^^ means variable length
>  ...
> 
>  int a[5][6], b[5];
> 
>  rowSum(5, 6, a, b,);
> 
>  ...
> 
>  void rowSum(int n, int m, int in[n][m], int out[n])
> 
>               //               ^^^^^^^^^ here we give names to the 
> lengths
>  {
>   for(int i=0; i<n; i++)
>   {
>     int sum=0;
> 
>     for(j=0; j<m; j++)
>       sum+=in[i][j];
> 
>     out[i]=sum;
>   }
> }
> 
> 
> 13) Old Fortran trick:
> 
>  struct s { int n; double d[]; };
> 
>  struct s *s1=malloc(sizeof(struct s)+64);
> 
>  s1->d[0]=...
> 
> Translation: We allocated space for the struct and 64 bytes for the 
> double
> type array.
> 
> 
> 14) Exact width integers: int_least_8t (also 16, 32, 64)
>                           uint_least_8t (also 16, 32, 64)
> 
>     Fast minimum width integers: int_fast_8t (also 16, 32, 64)
>                                  uint_fast_8t (also 16, 32, 64)
> 
>     Greatest width integers (the largest integer): intmax_t, 
> uintmax_t.
> 
> 
> 15) restricted pointers. They assure that no other pointer points to 
> the
> same data.
> 
> There are many other changes too. I got all these from
> http://www.freshsources.com/dev/Forums/C99/
> 
> Go and take a look there, it has a summary of the changes.
> 
> I would like to see what the others (you) believe about these 
> improvements.
> 
> 
> Ioannis
> 
> > -----Original Message-----
> > From: dev...@li...
> > [mailto:dev...@li...]On Behalf Of 
> James
> > Gordon
> > Sent: Tuesday, January 02, 2001 3:54 PM
> > To: 'dev...@li...'
> > Subject: RE: [Dev-C++] C99
> >
> >
> > For instance?
> >
> > Regards,
> >
> > James.
> >
> >
> >
> > -----Original Message-----
> > From: Ioannis Vranos [mailto:no...@ya...]
> > Sent: Saturday, December 30, 2000 12:17 PM
> > To: Dev-C++
> > Subject: [Dev-C++] C99
> >
> >
> > Talking about C, has anybody in here realized what crap has been
> > introduced
> > in C, in C99 standard? The language has been totally ruined. Now 
> i
> > completely understand why K&R will not write a new book.
> >
> >
> > Ioannis
> >
> > * Ioannis Vranos
> > * Programming pages: http://members.nbci.com/noicys
> > <http://members.nbci.com/noicys>
> > * Alternative URL: http://run.to/noicys <http://run.to/noicys>
> >
> >
> >
> >
> > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
> *
> > This electronic message and any attachment is intended to be
> > read by the named addressee(s) only.
> > Any other recipient should be aware that its contents may be
> > legally privileged and/or confidential and that its use,
> > disclosure, copying or distribution may be unlawful.
> > Unless you are a named addressee, please delete this message
> >
> > Whilst C. & J. Clark International Limited has taken steps
> > to prevent the transmission of computer viruses with electronic 
> mail,
> > responsibility for screening incoming messages and the risk of 
> such
> > transmission and its consequences lies with the recipient.
> >
> > C. & J. Clark International Limited
> > Registered in England and Wales
> > Company No. 141015
> > Registered Office: 40 High Street, Street, Somerset BA16 0YA
> > Telephone: +44 (0) 1458 443131
> > Fax: +44 (0) 1458 447547
> >
> >
> > _______________________________________________
> > Dev-cpp-users mailing list
> > Dev...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dev-cpp-users
> >
> 
> 
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> http://lists.sourceforge.net/mailman/listinfo/dev-cpp-users
> 

_______________________________________________
Dev-cpp-users mailing list
Dev...@li...
http://lists.sourceforge.net/mailman/listinfo/dev-cpp-users


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
This electronic message and any attachment is intended to be 
read by the named addressee(s) only. 
Any other recipient should be aware that its contents may be 
legally privileged and/or confidential and that its use, 
disclosure, copying or distribution may be unlawful. 
Unless you are a named addressee, please delete this message 

Whilst C. & J. Clark International Limited has taken steps 
to prevent the transmission of computer viruses with electronic mail, 
responsibility for screening incoming messages and the risk of such 
transmission and its consequences lies with the recipient. 

C. & J. Clark International Limited 
Registered in England and Wales 
Company No. 141015 
Registered Office: 40 High Street, Street, Somerset BA16 0YA 
Telephone: +44 (0) 1458 443131 
Fax: +44 (0) 1458 447547