On Thu, Jun 12, 2003 at 03:12:32PM -0700, Austin Hastings wrote:
>
> sub Ficp400::SaveRow(Int $p_row)
> {
> return if IsDeleted($p_row);
> }
*laugh* Well, yes, there is always the obvious way. I had wanted
something that would be reusable between multiple function, though
(sorry, should have
--- Austin Hastings <[EMAIL PROTECTED]> wrote:
>
> --- David Storrs <[EMAIL PROTECTED]> wrote:
> > So, as I sweat here in the salt mines of C++, longing for the
> > cleansing joy that Perl(5 or 6, I'd even take 4) is, I find myself
> > with the following problem:
> >
> > Frequently, I find mysel
--- David Storrs <[EMAIL PROTECTED]> wrote:
> So, as I sweat here in the salt mines of C++, longing for the
> cleansing joy that Perl(5 or 6, I'd even take 4) is, I find myself
> with the following problem:
>
> Frequently, I find myself writing stuff like this:
>
> void Ficp400::SaveRow(long p_r
So, as I sweat here in the salt mines of C++, longing for the
cleansing joy that Perl(5 or 6, I'd even take 4) is, I find myself
with the following problem:
Frequently, I find myself writing stuff like this:
void Ficp400::SaveRow(long p_row)
{
// if p_row is marked as deleted, return
Nicholas Clark wrote:
>
> class Foo {
> ...
> std::size_t spare = 0
> std::size_t allocate = 4096
> std::size_t min_readline = 80
>
> and have the compiler know that if I specify a member initialiser in my
> my constructor, then that should be used, otherwise to default to using
>
IIRC objects are in the future. However, I'm currently writing C++ and
keep finding something annoying that I'd like to be able to do easily.
I have objects with attributes, such as
class Foo {
...
std::size_t spare;
std::size_t allocate;
std::size_t min_readline;
and then I have
