C++ 中的装箱实现与STL
这是我第一次使用这个网站,对于任何错误的格式或奇怪的表述感到抱歉,我会尽力遵守这个网站的规则,但一开始我可能会犯一些错误。
我现在正在使用 STL 容器在 C++ 中实现一些不同的装箱算法。在当前的代码中,我仍然有一些逻辑错误需要修复,但这个问题更多的是关于程序的结构。我不想就如何构建程序以最大限度地减少逻辑错误的数量并使其尽可能易于阅读提出第二意见。在目前的状态下,我只是觉得这不是最好的方法,但我现在确实没有看到任何其他方法来编写我的代码。
该问题是一个动态在线装箱问题。它是动态的,因为物品在离开它们被分配到的垃圾箱之前有任意时间。
简而言之,我的问题是:
在 C++ 中,装箱算法的结构如何?
STL 容器是一个使实现能够处理任意长度输入的好工具吗?
我应该如何以良好、易于阅读和实施的方式处理容器?
关于我自己的代码的一些想法:
使用类可以很好地区分处理不同垃圾箱的列表和这些垃圾箱中的项目列表。
尽可能有效地实施。
易于运行大量不同的数据长度和文件进行基准测试。
#include <iostream>
#include <fstream>
#include <list>
#include <queue>
#include <string>
#include <vector>
using namespace std;
struct type_item {
int size;
int life;
bool operator < (const type_item& input)
{
return size < input.size;
}
};
class Class_bin {
double load;
list<type_item> contents;
list<type_item>::iterator i;
public:
Class_bin ();
bool operator < (Class_bin);
bool full (type_item);
void push_bin (type_item);
double check_load ();
void check_dead ();
void print_bin ();
};
Class_bin::Class_bin () {
load=0.0;
}
bool Class_bin::operator < (Class_bin input){
return load < input.load;
}
bool Class_bin::full (type_item input) {
if (load+(1.0/(double) input.size)>1) {
return false;
}
else {
return true;
}
}
void Class_bin::push_bin (type_item input) {
int sum=0;
contents.push_back(input);
for (i=contents.begin(); i!=contents.end(); ++i) {
sum+=i->size;
}
load+=1.0/(double) sum;
}
double Class_bin::check_load () {
return load;
}
void Class_bin::check_dead () {
for (i=contents.begin(); i!=contents.end(); ++i) {
i->life--;
if (i->life==0) {
contents.erase(i);
}
}
}
void Class_bin::print_bin () {
for (i=contents.begin (); i!=contents.end (); ++i) {
cout << i->size << " ";
}
}
class Class_list_of_bins {
list<Class_bin> list_of_bins;
list<Class_bin>::iterator i;
public:
void push_list (type_item);
void sort_list ();
void check_dead ();
void print_list ();
private:
Class_bin new_bin (type_item);
bool comparator (type_item, type_item);
};
Class_bin Class_list_of_bins::new_bin (type_item input) {
Class_bin temp;
temp.push_bin (input);
return temp;
}
void Class_list_of_bins::push_list (type_item input) {
if (list_of_bins.empty ()) {
list_of_bins.push_front (new_bin(input));
return;
}
for (i=list_of_bins.begin (); i!=list_of_bins.end (); ++i) {
if (!i->full (input)) {
i->push_bin (input);
return;
}
}
list_of_bins.push_front (new_bin(input));
}
void Class_list_of_bins::sort_list () {
list_of_bins.sort();
}
void Class_list_of_bins::check_dead () {
for (i=list_of_bins.begin (); i !=list_of_bins.end (); ++i) {
i->check_dead ();
}
}
void Class_list_of_bins::print_list () {
for (i=list_of_bins.begin (); i!=list_of_bins.end (); ++i) {
i->print_bin ();
cout << "\n";
}
}
int main () {
int i, number_of_items;
type_item buffer;
Class_list_of_bins bins;
queue<type_item> input;
string filename;
fstream file;
cout << "Input file name: ";
cin >> filename;
cout << endl;
file.open (filename.c_str(), ios::in);
file >> number_of_items;
for (i=0; i<number_of_items; ++i) {
file >> buffer.size;
file >> buffer.life;
input.push (buffer);
}
file.close ();
while (!input.empty ()) {
buffer=input.front ();
input.pop ();
bins.push_list (buffer);
}
bins.print_list ();
return 0;
}
请注意,这只是我的代码的快照,尚未正常运行
不想用不相关的闲聊来混淆它,只是想感谢做出贡献的人,我会审查我的代码,希望能够更好地构建我的编程
This is my first time using this site so sorry for any bad formatting or weird formulations, I'll try my best to conform to the rules on this site but I might do some misstakes in the beginning.
I'm right now working on an implementation of some different bin packing algorithms in C++ using the STL containers. In the current code I still have some logical faults that needs to be fixed but this question is more about the structure of the program. I would wan't some second opinion on how you should structure the program to minimize the number of logical faults and make it as easy to read as possible. In it's current state I just feel that this isn't the best way to do it but I don't really see any other way to write my code right now.
The problem is a dynamic online bin packing problem. It is dynamic in the sense that items have an arbitrary time before they will leave the bin they've been assigned to.
In short my questions are:
How would the structure of a Bin packing algorithm look in C++?
Is STL containers a good tool to make the implementation be able to handle inputs of arbitrary lenght?
How should I handle the containers in a good, easy to read and implement way?
Some thoughts about my own code:
Using classes to make a good distinction between handling the list of the different bins and the list of items in those bins.
Getting the implementation as effective as possible.
Being easy to run with a lot of different data lengths and files for benchmarking.
#include <iostream>
#include <fstream>
#include <list>
#include <queue>
#include <string>
#include <vector>
using namespace std;
struct type_item {
int size;
int life;
bool operator < (const type_item& input)
{
return size < input.size;
}
};
class Class_bin {
double load;
list<type_item> contents;
list<type_item>::iterator i;
public:
Class_bin ();
bool operator < (Class_bin);
bool full (type_item);
void push_bin (type_item);
double check_load ();
void check_dead ();
void print_bin ();
};
Class_bin::Class_bin () {
load=0.0;
}
bool Class_bin::operator < (Class_bin input){
return load < input.load;
}
bool Class_bin::full (type_item input) {
if (load+(1.0/(double) input.size)>1) {
return false;
}
else {
return true;
}
}
void Class_bin::push_bin (type_item input) {
int sum=0;
contents.push_back(input);
for (i=contents.begin(); i!=contents.end(); ++i) {
sum+=i->size;
}
load+=1.0/(double) sum;
}
double Class_bin::check_load () {
return load;
}
void Class_bin::check_dead () {
for (i=contents.begin(); i!=contents.end(); ++i) {
i->life--;
if (i->life==0) {
contents.erase(i);
}
}
}
void Class_bin::print_bin () {
for (i=contents.begin (); i!=contents.end (); ++i) {
cout << i->size << " ";
}
}
class Class_list_of_bins {
list<Class_bin> list_of_bins;
list<Class_bin>::iterator i;
public:
void push_list (type_item);
void sort_list ();
void check_dead ();
void print_list ();
private:
Class_bin new_bin (type_item);
bool comparator (type_item, type_item);
};
Class_bin Class_list_of_bins::new_bin (type_item input) {
Class_bin temp;
temp.push_bin (input);
return temp;
}
void Class_list_of_bins::push_list (type_item input) {
if (list_of_bins.empty ()) {
list_of_bins.push_front (new_bin(input));
return;
}
for (i=list_of_bins.begin (); i!=list_of_bins.end (); ++i) {
if (!i->full (input)) {
i->push_bin (input);
return;
}
}
list_of_bins.push_front (new_bin(input));
}
void Class_list_of_bins::sort_list () {
list_of_bins.sort();
}
void Class_list_of_bins::check_dead () {
for (i=list_of_bins.begin (); i !=list_of_bins.end (); ++i) {
i->check_dead ();
}
}
void Class_list_of_bins::print_list () {
for (i=list_of_bins.begin (); i!=list_of_bins.end (); ++i) {
i->print_bin ();
cout << "\n";
}
}
int main () {
int i, number_of_items;
type_item buffer;
Class_list_of_bins bins;
queue<type_item> input;
string filename;
fstream file;
cout << "Input file name: ";
cin >> filename;
cout << endl;
file.open (filename.c_str(), ios::in);
file >> number_of_items;
for (i=0; i<number_of_items; ++i) {
file >> buffer.size;
file >> buffer.life;
input.push (buffer);
}
file.close ();
while (!input.empty ()) {
buffer=input.front ();
input.pop ();
bins.push_list (buffer);
}
bins.print_list ();
return 0;
}
Note that this is just a snapshot of my code and is not yet running properly
Don't wan't to clutter this with unrelated chatter just want to thank the people who contributed, I will review my code and hopefully be able to structure my programming a bit better
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
好吧,理想情况下,您将有几种装箱算法,分为不同的函数,其区别仅在于算法的逻辑。该算法应该在很大程度上独立于数据的表示,因此您只需调用一次函数即可更改算法。
您可以查看 STL 算法 的共同点。主要是,它们在迭代器而不是容器上操作,但正如我在下面详细介绍的,我最初不会建议您这样做。您应该了解哪些算法可用,并在您的实现中利用它们。
它通常是这样工作的:创建一个容器,填充容器,对容器应用算法。
从你的需求描述来看,这就是你将如何使用它,所以我认为它会很好。装箱算法和大多数 STL 算法之间有一个重要区别。
STL 算法要么是非修改的,要么是将元素插入到目标的。另一方面,装箱是“这里有一个垃圾箱列表,使用它们或添加一个新的垃圾箱”。使用迭代器并非不可能做到这一点,但可能不值得付出努力。我首先对容器进行操作,获取一个工作程序,对其进行备份,然后看看是否可以使其仅适用于迭代器。
我会采用这种方法,描述您的输入和输出的特征:
然后我会担心“我的算法需要做什么?”
Class_bin
很好地封装了所需的内容。目前还不清楚生命(或死亡)的用途。我无法想象这个概念与实现装箱算法相关。也许应该把它排除在外?
这是个人喜好,但我不喜欢为我的对象提供
operator<
。对象通常是不平凡的并且具有许多小于的含义。例如,一种算法可能希望所有活动项目都排序在死亡项目之前。为了清楚起见,我通常将其包装在另一个结构中:Class_
前缀 - 它只是有点过多,并且从代码中应该可以清楚地看出。 (这是匈牙利表示法的变体。程序员往往对它怀有敌意。)i
(迭代器)。它不是阶级状态的一部分。如果您在所有成员中都需要它,那没问题,只需在那里重新声明即可。如果输入太长,请使用typedef
。运算符<
。bool full(type_item)
有点误导。我可能会使用bool can_hold(type_item)
。对我来说,如果剩余空间为零,bool full()
将返回 true。check_load()
命名为load()
看起来更清楚。check_dead()
应该完成什么任务。print_bin
并将其编写为非成员函数,以保持对象更干净。sort_list
可以替换为std::sort
。comparator
这个名字太通用了,它没有给出比较什么或为什么比较的指示,所以考虑更清楚一些。总体而言,我认为您选择的类充分模拟了您想要表示的空间,所以您会没事的。
我可能会这样构建我的项目:
Well, ideally you would have several bin-packing algorithms, separated into different functions, which differ only by the logic of the algorithm. That algorithm should be largely independent from the representation of your data, so you can change your algorithm with only a single function call.
You can look at what the STL Algorithms have in common. Mainly, they operate on iterators instead of containers, but as I detail below, I wouldn't suggest this for you initially. You should get a feel for what algorithms are available and leverage them in your implementation.
It usually works like this: create a container, fill the container, apply an algorithm to the container.
Judging from the description of your requirements, that is how you'll use this, so I think it'll be fine. There's one important difference between your bin packing algorithm and most STL algorithms.
The STL algorithms are either non-modifying or are inserting elements to a destination. bin-packing, on the other hand, is "here's a list of bins, use them or add a new bin". It's not impossible to do this with iterators, but probably not worth the effort. I'd start by operating on the container, get a working program, back it up, then see if you can make it work for only iterators.
I'd take this approach, characterize your inputs and outputs:
Then I'd worry about "what does my algorithm need to do?"
Class_bin
is a good encapsulation of what is needed.It's unclear what
life
(or death) is used for. I can't imagine that concept being relevant to implementing a bin-packing algorithm. Maybe it should be left out?This is personal preference, but I don't like giving
operator<
to my objects. Objects are usually non-trivial and have many meanings of less-than. For example, one algorithm might want all the alive items sorted before the dead items. I typically wrap that in another struct for clarity:Class_
prefix on all your types - it's just a bit excessive, and it should be clear from the code. (This is a variant of hungarian notation. Programmers tend to be hostile towards it.)i
(the iterator). It's not part of class state. If you need it in all the members, that's ok, just redeclare it there. If it's too long to type, use atypedef
.operator<
.bool full(type_item)
is a little misleading. I'd probably usebool can_hold(type_item)
. To me,bool full()
would return true if there is zero space remaining.check_load()
would seem more clearly namedload()
.check_dead()
is supposed to accomplish.print_bin
and write that as a non-member function, to keep your objects cleaner.sort_list
can be replaced withstd::sort
.comparator
is too generic a name, it gives no indication of what it compares or why, so consider being more clear.Overall, I think the classes you've picked adequately model the space you're trying to represent, so you'll be fine.
I might structure my project like this:
一些想法:
你的名字有些地方有点混乱。
考虑到 life 和 load 的参数,我很困惑正在做。我熟悉的装箱问题只是有尺寸。我猜随着时间的推移,一些物品会从垃圾箱中取出并消失?
关于你的类 Class_list_of_bins 的一些进一步的想法
是将太多的自身暴露给外界。为什么外界要check_dead或者sort_list呢?这与任何人无关,只与物体本身有关。您应该在该类上拥有的公共方法确实应该类似于
* 将一个项目添加到垃圾箱集合中
* 打印解决方案
* 一步步走向未来
糟糕,糟糕,糟糕!不要将成员变量放在您的身上,除非它们实际上是成员国。您应该在使用迭代器的地方定义它。如果您想节省一些输入,请添加以下内容: typedef list::iterator bin_iterator ,然后使用 bin_iterator 作为类型。
扩展答案
这是我的伪代码:
一些快速说明:
Some thoughts:
Your names are kinda messed up in places.
I'm confused given the parameters of life and load as to what you are doing. The bin packing problem I'm familiar with just has sizes. I'm guessing that overtime some of the objects are taken out of bins and thus go away?
Some further thoughts on your classes
Class_list_of_bins is exposing too much of itself to the outside world. Why would the outside world want to check_dead or sort_list? That's nobodies business but the object itself. The public method you should have on that class really should be something like
* Add an item to the collection of bins
* Print solution
* Step one timestep into the future
Bad, bad, bad! Don't put member variables on your unless they are actually member states. You should define that iterator where it is used. If you want to save some typing add this: typedef list::iterator bin_iterator and then you use bin_iterator as the type instead.
EXPANDED ANSWER
Here is my psuedocode:
Some quick notes:
这次采访深入了解了 STL 背后的基本原理。这可能会给您一些关于如何以 STL 方式实现算法的灵感。
This interview gives some great insight into the rationale behind the STL. This may give you some inspiration on how to implement your algorithms the STL-way.