[ace-users] ACE_Ini_ImpExp: Feature Request?

Kyle Brost

unread,

Sep 24, 2001, 11:10:32 AM9/24/01

to

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1450A.AAFD96E0
Content-Type: text/plain

I have been looking at ACE_Ini_ImpExp and I noticed that the import and
export routines do not handle the comments in a "safe" manner. When you
read in the file, the import_config method ignores comment lines. When you
write the file out, all the information is written back to the file without
the original comments. Was this an oversight or an area where there needs
to be some modifications?

Also, I found the following lines in the 'Configuration.cpp' source:
// Can remove this when import_config and export_config are removed
from
// ACE_Configuration. They're deprecated at ACE 5.2.
#include "ace/Configuration_Import_Export.h"
What will be replacing the functionality of the import and export
functionality for 'ini'/'conf' files?

Thanks,

Kyle Brost
----

------_=_NextPart_001_01C1450A.AAFD96E0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2652.35">
<TITLE>ACE_Ini_ImpExp: Feature Request?</TITLE>
</HEAD>
<BODY>

I have been looking at ACE_Ini_ImpExp and I noticed =
that the import and export routines do not handle the comments in a =
"safe" manner.  When you read in the file, the =
import_config method ignores comment lines.  When you write the =
file out, all the information is written back to the file without the =
original comments.  Was this an oversight or an area where there =
needs to be some modifications?

Also, I found the following lines in the =
'Configuration.cpp' source: 
         // Can =
remove this when import_config and export_config are removed =
from
         // =
ACE_Configuration. They're deprecated at ACE 5.2.
         #include =
"ace/Configuration_Import_Export.h"
 What will be replacing the functionality of the =
import and export functionality for 'ini'/'conf' files?

Thanks,

Kyle Brost
 ----

</BODY>
</HTML>
------_=_NextPart_001_01C1450A.AAFD96E0--

Steve Huston

unread,

Sep 24, 2001, 1:12:17 PM9/24/01

to

Hi Kyle,

> I have been looking at ACE_Ini_ImpExp and I noticed that the import and
> export routines do not handle the comments in a "safe" manner. When you
> read in the file, the import_config method ignores comment lines. When
you
> write the file out, all the information is written back to the file
without
> the original comments. Was this an oversight or an area where there needs
> to be some modifications?

I didn't write this, but it was probably a "why do you need to do that?"
sort of thing. If you have a program to maintain the config (doing exports)
then you don't need to be editing it. If you edit it (and put in comments)
you don't need to export it.

If you'd like to add support for maintaining comments, send updated code to
this list.

> Also, I found the following lines in the 'Configuration.cpp' source:
> // Can remove this when import_config and export_config are removed
> from
> // ACE_Configuration. They're deprecated at ACE 5.2.
> #include "ace/Configuration_Import_Export.h"
> What will be replacing the functionality of the import and export
> functionality for 'ini'/'conf' files?

That I did add. The import/export functionality is moved out to other
classes that offer both ini and registry-format import/export. That is meant
to replace to one-dimensional ACE_Configuration::import and export methods.
The existing import and export methods are left there for compatibility.

Best regards,

-Steve

--
Steve Huston Riverace Corporation
Email: shu...@riverace.com http://www.riverace.com
ACE Kits, Support, Consulting (508) 541-9180, FAX 541-9185
Installable Kits at http://www.riverace.com/ACE_Kits/kit-store.html

Kyle Brost

unread,

Sep 24, 2001, 1:31:42 PM9/24/01

to

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1451E.0497B0B0
Content-Type: text/plain;
charset="iso-8859-1"

Thanks Steve,

I noticed that there is a "ACE_Configuration_Win32Registry" implementation
for Win32 Registries, but I could not find the forward looking
implementation for INI files. Does this exist? If so, could you point me
in the correct direction. If not... It could be an interesting task.

Thanks,

Kyle Brost
----

Hi Kyle,

Best regards,

-Steve

------_=_NextPart_001_01C1451E.0497B0B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =

charset=3Diso-8859-1">

<TITLE>RE: [ace-users] ACE_Ini_ImpExp: Feature Request?</TITLE>
</HEAD>
<BODY>

Thanks Steve,

I noticed that there is a =
"ACE_Configuration_Win32Registry" implementation for Win32 =
Registries, but I could not find the forward looking implementation for =
INI files.  Does this exist?  If so, could you point me in =
the correct direction.  If not...  It could be an interesting =
task.

Thanks,

Kyle Brost
 ----

-----Original Message-----
 From: Steve Huston [<A =
HREF=3D"mailto:shu...@riverace.com">mailto:shu...@riverace.com</A>]</F=
ONT>
 Sent: Monday, September 24, 2001 11:08 AM
 To: ace-...@cs.wustl.edu
 Subject: Re: [ace-users] ACE_Ini_ImpExp: Feature =
Request?

Hi Kyle,

> I have been looking at ACE_Ini_ImpExp and I =
noticed that the import and
 > export routines do not handle the comments in a =
"safe" manner.  When you
 > read in the file, the import_config method =
ignores comment lines.  When
 you
 > write the file out, all the information is =
written back to the file
 without
 > the original comments.  Was this an =
oversight or an area where there needs
 > to be some modifications?

I didn't write this, but it was probably a "why =
do you need to do that?"
 sort of thing. If you have a program to maintain the =
config (doing exports)
 then you don't need to be editing it. If you edit it =
(and put in comments)
 you don't need to export it.

If you'd like to add support for maintaining =
comments, send updated code to
 this list.

> Also, I found the following lines in the =
'Configuration.cpp' source:
 > // Can remove this when import_config and =
export_config are removed
 > from
 > // ACE_Configuration. They're deprecated at ACE =
5.2.
 > #include =
"ace/Configuration_Import_Export.h"
 > What will be replacing the functionality of the =
import and export
 > functionality for 'ini'/'conf' files?

That I did add. The import/export functionality is =
moved out to other
 classes that offer both ini and registry-format =
import/export. That is meant
 to replace to one-dimensional =
ACE_Configuration::import and export methods.
 The existing import and export methods are left =
there for compatibility.

Best regards,

-Steve

--
 Steve =
Huston           =
            =
       Riverace Corporation
 Email: =
shu...@riverace.com        &nbs=
p;      <A HREF=3D"http://www.riverace.com" =
TARGET=3D"_blank">http://www.riverace.com</A>
 ACE Kits, Support, =
Consulting          &n=
bsp;  (508) 541-9180, FAX 541-9185
 Installable Kits at <A =
HREF=3D"http://www.riverace.com/ACE_Kits/kit-store.html" =
TARGET=3D"_blank">http://www.riverace.com/ACE_Kits/kit-store.html</A></F=
ONT>

</BODY>
</HTML>
------_=_NextPart_001_01C1451E.0497B0B0--

Steve Huston

unread,

Sep 24, 2001, 3:51:18 PM9/24/01

to

Hi Kyle,

> Thanks Steve,

You're welcome.

> I noticed that there is a "ACE_Configuration_Win32Registry" implementation
> for Win32 Registries, but I could not find the forward looking
> implementation for INI files. Does this exist? If so, could you point me
> in the correct direction. If not... It could be an interesting task.

I'm not sure what you mean by "forward looking". The Win32 registry version
works directly on the Win32 registry, as opposed to being in memory and
needing an import/export to get and store data.

Could you explain a bit more about what you're looking for?

Kyle Brost

unread,

Sep 24, 2001, 4:01:36 PM9/24/01

to

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C14533.3D199560
Content-Type: text/plain;
charset="iso-8859-1"

Hello Steve,

I would like the same functionality that is provided by the ACE_Ini_ImpExp
with the additional comment support. I took the comment in the source file
to mean that ACE_Ini_ImpExp will be removed in 5.2 and that the ability to
read flat configuration files would have to be achieved by using the
ACE_Configuration_XXX classes. So, 1) Is there a different class, besides
ACE_Ini_ImpExp, that provides flat-configuration file reading and writing?
2) Will ACE_Ini_ImpExp become depreciated?

I hope that better explains my questions. Modifying the code to enable
comment retention is not difficult and that something that I think I can
handle if we choose to use ACE in the near future.

Thanks,

Kyle Brost
----

-----Original Message-----
From: Steve Huston [mailto:shu...@riverace.com]
Sent: Monday, September 24, 2001 1:46 PM
To: ace-...@cs.wustl.edu
Subject: Re: [ace-users] ACE_Ini_ImpExp: Feature Request?

Hi Kyle,

> Thanks Steve,

You're welcome.

-Steve

------_=_NextPart_001_01C14533.3D199560

Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2652.35">
<TITLE>RE: [ace-users] ACE_Ini_ImpExp: Feature Request?</TITLE>
</HEAD>
<BODY>

Hello Steve,

I would like the same functionality that is provided =
by the ACE_Ini_ImpExp with the additional comment support.  I took =
the comment in the source file to mean that ACE_Ini_ImpExp will be =
removed in 5.2 and that the ability to read flat configuration files =
would have to be achieved by using the ACE_Configuration_XXX =
classes.  So, 1) Is there a different class, besides =
ACE_Ini_ImpExp, that provides flat-configuration file reading and =
writing? 2) Will ACE_Ini_ImpExp become depreciated?

I hope that better explains my questions.  =
Modifying the code to enable comment retention is not difficult and =
that something that I think I can handle if we choose to use ACE in the =
near future.

Thanks,

Kyle Brost
 ----

-----Original Message-----
 From: Steve Huston [<A =
HREF=3D"mailto:shu...@riverace.com">mailto:shu...@riverace.com</A>]</F=
ONT>

Sent: Monday, September 24, 2001 1:46 PM

To: ace-...@cs.wustl.edu
 Subject: Re: [ace-users] ACE_Ini_ImpExp: Feature =
Request?

Hi Kyle,

> Thanks Steve,

You're welcome.

> I noticed that there is a =
"ACE_Configuration_Win32Registry" implementation
 > for Win32 Registries, but I could not find the =
forward looking
 > implementation for INI files.  Does this =
exist?  If so, could you point me
 > in the correct direction.  If not...  =
It could be an interesting task.

I'm not sure what you mean by "forward =
looking".  The Win32 registry version
 works directly on the Win32 registry, as opposed to =
being in memory and
 needing an import/export to get and store =
data.

Could you explain a bit more about what you're =
looking for?

-Steve

--
 Steve =
Huston           =
            =
       Riverace Corporation
 Email: =
shu...@riverace.com        &nbs=
p;      <A HREF=3D"http://www.riverace.com" =
TARGET=3D"_blank">http://www.riverace.com</A>
 ACE Kits, Support, =
Consulting          &n=
bsp;  (508) 541-9180, FAX 541-9185
 Installable Kits at <A =
HREF=3D"http://www.riverace.com/ACE_Kits/kit-store.html" =
TARGET=3D"_blank">http://www.riverace.com/ACE_Kits/kit-store.html</A></F=
ONT>

</BODY>
</HTML>
------_=_NextPart_001_01C14533.3D199560--

Steve Huston

unread,

Sep 24, 2001, 4:08:09 PM9/24/01

to

RE: [ace-users] ACE_Ini_ImpExp: Feature Request?Hi Kyle,

> I would like the same functionality that is provided by the
> ACE_Ini_ImpExp with the additional comment support.

Ok.

> I took the comment in the source file to mean that ACE_Ini_ImpExp
> will be removed in 5.2 and that the ability to read flat configuration
files
> would have to be achieved by using the ACE_Configuration_XXX classes.

Ah, I see. No, that's not the case.

ACE_Ini_ImpExp is new for ACE 5.2 and will continue forward.
ACE_Configuration::import and ::export were in 5.1, and will be in 5.2, but
will probably be removed at the next version after 5.2 in favor of
explicitly using either the INI or registry file format.

> So, 1) Is there a different class, besides ACE_Ini_ImpExp, that provides
> flat-configuration file reading and writing?

Yes... ACE_Registry_ImpExp (not to be confused with
ACE_Configuration_Win32Registry). The Registry_ImpExp and Ini_ImpExp classes
use a different format in the text file, but both use text files.

> 2) Will ACE_Ini_ImpExp become depreciated?

No, as long as it works, it won't be depreciated. And it certainly won't be
deprecated ;-)

> I hope that better explains my questions.

Yes, thanks!

> Modifying the code to enable comment retention is not difficult and that
> something that I think I can handle if we choose to use ACE in the near
future.

Ok, great!

Take care,