STLSoft 1.7.1 released

I'm pleased (and very relieved) to announce that STLSoft version 1.7.1 is
released.

There are several major new features:
 - the .netSTL project, providing C++.NET / STL crossover
 - the InetSTL project, providing STL techniques for Internet programming
 - unit-testing incorporated into the libraries; this has caught an embarassing
number of issues; You'll find a unittest.cpp in the test directory for each
sub-project, which links to code in the ./unittest directory.
 - a whole swathe of new components in the STLSoft main project, and the UNIXSTL
and WinSTL sub-projects

There are some minor improvements:
 - the documentation has been tidied up to the degree that all classes,
functions, methods, etc. are indicated in the correct namespaces, etc.
 - removal of many non-standard macros and symbol names; there're more to come,
however

The things that have been postponed to the next release:
 - a really good overhaul of the introductory / expository documentation. Any
feedback on this from users would be most useful
 - provision of any more samples
 - provision of scripts to generate makefiles for the tests and sample programs

Now that this very major hurdle is behind us, I'm in the market for new feature requests and submissions, so please don't hold back. I hope to release 1.7.2 in a few weeks, and intend to do another big step with 1.8.1 before the end of the year - there are a lot of new features planned for that. :-)

Good coding


-- 
Matthew Wilson

Author: "Imperfect C++", Addison-Wesley, 2004
    (http://www.imperfectcplusplus.com)
Contributing editor, C/C++ Users Journal
    (http://www.synesis.com.au/articles.html#columns)
STLSoft moderator
    (http://www.stlsoft.org)

-------------------------------------------------------------------------------

"So far, C++ is the best language I've discovered to say what I want to say" -- Alex Stepanov

-------------------------------------------------------------------------------

> I'm pleased (and very relieved) to announce that STLSoft version 1.7.1 is > released. > > Now that this very major hurdle is behind us, I'm in the market for new feature > requests and submissions, so please don't hold back. I hope to release 1.7.2 in a > few weeks, and intend to do another big step with 1.8.1 before the end of the > year - there are a lot of new features planned for that. :-) module_directory, great clipboard stuff starting to appear window_visible_scope, great still missing insert/SetItemData for list/combo boxes you asked me to remind you about process_sequence auto_buffer's code states the default size at 256 while the textual description states it at 512 you think auto_destructor could be policied with the destruction function (I asked about this before but talking about smart pointers) ? winstl::resource_string isn't documented comstl::safe_array_sequence also not documented that's all for now... great work...

> module_directory, great Actually, I found a bug in it yesterday, after I'd done the release. Fixed for 1.7.2. As well as that, I've just been plugging in unittesting and proper documentation for it. That's going to be my strategy for getting this big bad baby properly documented: each time I edit a file I'll fix its doc + ensure the unittest is comprehensive. > clipboard stuff starting to appear Keep making those requests. > window_visible_scope, great Pleasure. :-) > still missing insert/SetItemData for list/combo boxes > you asked me to remind you about process_sequence Remind me again in a while > auto_buffer's code states the default size at 256 while the textual description states it at 512 Thanks. Now fixed (with 1.7.2) > you think auto_destructor could be policied with the destruction function (I asked about this before but talking about smart pointers) ? I don't remember. Can you explain what you mean? > winstl::resource_string isn't documented comstl::safe_array_sequence also not documented They are in the code. Is it not showing in the Docs? > that's all for now... Keep 'em coming > great work... Nice to be appreciated. ;)

> > clipboard stuff starting to appear > > Keep making those requests. clipboard_lock and read/writing are missing still... all I saw for now was clipboard_format_sequence > > still missing insert/SetItemData for list/combo boxes > > you asked me to remind you about process_sequence > > Remind me again in a while Sure... > > you think auto_destructor could be policied with the destruction function (I > > asked about this before but talking about smart pointers) ? > > I don't remember. Can you explain what you mean? That 'delete' could be made into a policy... so instead of deleting you could have, for example, ->Release, or something alike... I know there's a special ptr for COM, but that's not the point... say you're dealing with objects created by factories, and destruction isn't a plain delete but some special function... that's where the policy class would kick in... > > winstl::resource_string isn't documented comstl::safe_array_sequence also not documented > > They are in the code. Is it not showing in the Docs? No. Actually my original post was to say they weren't in, but I decided to check the code first, and there they were, so they're just missing in the docs > > that's all for now... > > Keep 'em coming I will...

Did basic_file_path_buffer loose it's automatic conversion to a mutable pointer? If so, module_directory doesn't work (it requires a small, very small tweak) is this the error you talked about in the other post?

Yep. Here it is "Pablo Aguilar" <paguilarg@hotmail.com> wrote in message news:cada25$2n5o$1@digitaldaemon.com... > Did basic_file_path_buffer loose it's automatic conversion to a mutable pointer? > > If so, module_directory doesn't work (it requires a small, very small tweak) is this the error you talked about in the other post? > >

This is now pretty much handled with scoped_handle. "Pablo Aguilar" <paguilarg@hotmail.com> wrote in message news:cad1n1$2b8a$1@digitaldaemon.com... >> > clipboard stuff starting to appear >> >> Keep making those requests. > > clipboard_lock and read/writing are missing still... all I saw for now > was > clipboard_format_sequence > >> > still missing insert/SetItemData for list/combo boxes >> > you asked me to remind you about process_sequence >> >> Remind me again in a while > > Sure... > >> > you think auto_destructor could be policied with the destruction > function (I >> > asked about this before but talking about smart pointers) ? >> >> I don't remember. Can you explain what you mean? > > That 'delete' could be made into a policy... so instead of deleting > you > could have, for example, ->Release, or something alike... I know > there's a > special ptr for COM, but that's not the point... say you're dealing > with > objects created by factories, and destruction isn't a plain delete but > some > special function... that's where the policy class would kick in... > >> > winstl::resource_string isn't documented comstl::safe_array_sequence also not documented >> >> They are in the code. Is it not showing in the Docs? > > No. Actually my original post was to say they weren't in, but I > decided to > check the code first, and there they were, so they're just missing in > the > docs > >> > that's all for now... >> >> Keep 'em coming > > I will... > >

Forums