Gregory Brown

Sorry for the very delayed response. I agree that this is a confusing behavior, and it's something I'm open to change. The bad news is that it's the officially documented...

Something like this will work, but I don't want to rely on generic APIs like `to_str`, because a meaningful string representation has little to do with a meaningful _color string_...

/cc @packetmonkey since this kind of stuff usually captures your interest.

Subclassing Ruby core classes is both bad design and can lead to unexpected internal errors because of optimizations at the language level, so I don't want to encourage it. There's...

@packetmonkey This solves a different problem, though. A custom color class would most likely be used for dynamic determination of colors, not color types! The change you suggested might be...

@slabounty: Returning a meaningful value wasn't ever documented anywhere, I don't think. So it's currently undefined behavior, and we can change it.

@slabounty For right now it'd probably be OK to convert into whatever PDF::Core wants. A patch to `PDF::Core` would also be alright, but there are many undefined or poorly defined...

@slabounty This hasn't been forgotten, it's just blocking on me. I think your patch proves the concept, but I'll want to change the interfaces a little bit, and won't know...

We need to more comprehensively think about what to allow / not allow before a page is created. But I agree that we should at least be consistent, and for...

Your assumptions sound correct, and I think the core problem is that `float` is very naive in how it works: it keeps track of what page you start on and...