Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #139208 > unrolled thread

if cargo blocks

Back to article view | Back to comp.lang.c

Contents

  if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-29 10:42 -0500
    Re: if cargo blocks David Brown <david.brown@hesbynett.no> - 2018-12-29 17:26 +0100
      Re: if cargo blocks Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2018-12-29 16:32 +0000
    Re: if cargo blocks Bart <bc@freeuk.com> - 2018-12-29 16:56 +0000
      Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-29 12:34 -0500
        Re: if cargo blocks Bart <bc@freeuk.com> - 2018-12-29 23:49 +0000
          Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-29 18:52 -0500
            Re: if cargo blocks Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2018-12-30 00:12 +0000
            Re: if cargo blocks rbowman <bowman@montana.com> - 2018-12-29 19:04 -0700
              Re: if cargo blocks Ralf Goertz <me@myprovider.invalid> - 2018-12-30 06:12 +0100
                Re: if cargo blocks David Brown <david.brown@hesbynett.no> - 2018-12-30 15:23 +0100
                  Language (Was: if cargo blocks) gazelle@shell.xmission.com (Kenny McCormack) - 2018-12-30 15:39 +0000
                    Re: Language (Was: if cargo blocks) rbowman <bowman@montana.com> - 2018-12-30 11:23 -0700
                  Re: if cargo blocks Ralf Goertz <me@myprovider.invalid> - 2018-12-31 05:21 +0100
                    Re: if cargo blocks David Brown <david.brown@hesbynett.no> - 2018-12-31 18:09 +0100
                      Re: if cargo blocks rbowman <bowman@montana.com> - 2018-12-31 12:22 -0700
                      Re: if cargo blocks Ralf Goertz <me@myprovider.invalid> - 2019-01-01 12:04 +0100
                    Re: if cargo blocks rbowman <bowman@montana.com> - 2018-12-31 11:50 -0700
                      Re: if cargo blocks Ralf Goertz <me@myprovider.invalid> - 2019-01-01 11:43 +0100
                        Re: if cargo blocks Ralf Goertz <me@myprovider.invalid> - 2019-01-01 14:27 +0100
                          German grammar (Was: if cargo blocks) gazelle@shell.xmission.com (Kenny McCormack) - 2019-01-01 14:17 +0000
                          Re: if cargo blocks rbowman <bowman@montana.com> - 2019-01-01 11:04 -0700
                            Re: if cargo blocks fir <profesor.fir@gmail.com> - 2019-01-01 10:38 -0800
                        Re: if cargo blocks rbowman <bowman@montana.com> - 2019-01-01 10:57 -0700
                          DDR Ralf Goertz <me@myprovider.invalid> - 2019-01-01 21:18 +0100
                            Re: DDR rbowman <bowman@montana.com> - 2019-01-01 16:18 -0700
                  Re: if cargo blocks Siri Cruise <chine.bleu@yahoo.com> - 2019-01-01 16:30 -0800
                Re: if cargo blocks rbowman <bowman@montana.com> - 2018-12-30 11:09 -0700
                  Re: if cargo blocks Ralf Goertz <me@myprovider.invalid> - 2018-12-31 05:43 +0100
                    Re: if cargo blocks rbowman <bowman@montana.com> - 2018-12-31 12:06 -0700
                Linguistics. Re: if cargo blocks Siri Cruise <chine.bleu@yahoo.com> - 2019-01-01 16:27 -0800
                  Re: Linguistics. Re: if cargo blocks rbowman <bowman@montana.com> - 2019-01-01 22:30 -0700
                    Re: Linguistics. Re: if cargo blocks Louis Krupp <lkrupp@nospam.pssw.com.invalid> - 2019-01-02 04:18 -0700
            Re: if cargo blocks Bart <bc@freeuk.com> - 2018-12-30 02:07 +0000
              Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-29 21:59 -0500
    Re: if cargo blocks rbowman <bowman@montana.com> - 2018-12-29 13:57 -0700
      Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-29 16:03 -0500
        Re: if cargo blocks Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2018-12-29 21:32 +0000
        Re: if cargo blocks rbowman <bowman@montana.com> - 2018-12-29 16:06 -0700
          Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-29 18:15 -0500
            Re: if cargo blocks fir <profesor.fir@gmail.com> - 2018-12-29 15:32 -0800
              Re: if cargo blocks fir <profesor.fir@gmail.com> - 2018-12-29 15:34 -0800
                Re: if cargo blocks fir <profesor.fir@gmail.com> - 2018-12-29 15:38 -0800
                Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-29 15:40 -0800
                  Re: if cargo blocks fir <profesor.fir@gmail.com> - 2018-12-29 15:45 -0800
              Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-29 18:36 -0500
                Re: if cargo blocks fir <profesor.fir@gmail.com> - 2018-12-29 15:42 -0800
                  Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-29 15:45 -0800
                    Re: if cargo blocks fir <profesor.fir@gmail.com> - 2018-12-29 15:54 -0800
                      Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-29 18:58 -0500
                        Re: if cargo blocks fir <profesor.fir@gmail.com> - 2018-12-29 16:01 -0800
      Re: if cargo blocks "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2018-12-29 13:36 -0800
    Re: if cargo blocks "I Set My Girlfriend's Pantyhose on Fire" <cdalten@gmail.com> - 2018-12-29 13:16 -0800
      Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-29 16:32 -0500
    Re: if cargo blocks Siri Cruise <chine.bleu@yahoo.com> - 2018-12-30 13:00 -0800
      Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-30 16:12 -0500
        Re: if cargo blocks Siri Cruise <chine.bleu@yahoo.com> - 2018-12-30 13:31 -0800
          Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-30 16:45 -0500
            Re: if cargo blocks Bart <bc@freeuk.com> - 2018-12-30 22:17 +0000
              Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-30 17:22 -0500
                Re: if cargo blocks "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2018-12-30 20:25 -0800
    Re: if cargo blocks Ian Collins <ian-news@hotmail.com> - 2019-01-03 09:50 +1300
      Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-01-02 15:54 -0500
        Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-01-02 16:29 -0500
          Re: if cargo blocks mark.bluemel@gmail.com - 2019-01-03 00:44 -0800
            Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-01-03 08:17 -0500
              Re: if cargo blocks mark.bluemel@gmail.com - 2019-01-03 05:40 -0800
                Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-01-03 09:15 -0500
              You are so full of shit (Was: if cargo blocks) gazelle@shell.xmission.com (Kenny McCormack) - 2019-01-03 13:42 +0000
              Re: if cargo blocks fir <profesor.fir@gmail.com> - 2019-01-03 12:27 -0800
          Re: if cargo blocks Ian Collins <ian-news@hotmail.com> - 2019-01-04 11:11 +1300
            Re: if cargo blocks "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2019-01-03 14:37 -0800
            Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-01-03 17:48 -0500
            Re: if cargo blocks fir <profesor.fir@gmail.com> - 2019-01-03 14:59 -0800
        Re: if cargo blocks mark.bluemel@gmail.com - 2019-01-03 00:44 -0800
          Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-01-03 08:19 -0500
            Re: if cargo blocks mark.bluemel@gmail.com - 2019-01-03 05:43 -0800
              Re: if cargo blocks "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-01-03 05:51 -0800
            Re: if cargo blocks "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2019-01-03 13:22 -0800
        Re: if cargo blocks Ian Collins <ian-news@hotmail.com> - 2019-01-04 11:10 +1300

Page 4 of 4 — ← Prev page 1 2 3 [4]

#139273

On 12/30/2018 2:22 PM, Rick C. Hodgin wrote:
> On 12/30/2018 5:17 PM, Bart wrote:
>> On 30/12/2018 21:45, Rick C. Hodgin wrote:
>>> It only makes sense.  It is another of those fundamental operations
>>> that is not easily provided for in C/C++ today (without extensions
>>> like those seen in GNU).
>>>
>>> CAlive's goal is to provide for fundamental abilities.  None of the
>>> atypical ones have to be used by anyone.  But, if you want to use
>>> them in certain cases ... they'll be there.  I probably won't use
>>> many of the new features I'm adding most of the time, but I will
>>> probably use most of them some of the time.
>>
>> The reference is to Algol68 where there is no distinction between 
>> statements and expressions, which could be used interchangeably.
>>
>> This is what I meant the other day about adding fewer, more general, 
>> broader features rather than dozens of very specific ones.
>>
>> Actually, my language until about six or so years ago worked exactly 
>> the same way. My newer one doesn't - it is more conservative and 
>> limited by design.
>>
>> Because (1) I hardly ever used those features; (2) avoiding them leads 
>> to easier-to-understand code IMO; (3) it makes code and algorithms 
>> more portable; (4) it makes the language easier to implement; (5) it 
>> makes it easier to trap a range of errors that otherwise have to be 
>> let through.
> 
> My goals with CAlive are the needs of development by other people.  I
> want to give them a robust set of tools in version 1.0.  If, in by the
> time version 5.0 is released some of the features are not in use and
> not needed, I may consider removing them.  However, my general phil-
> osophy is that once something is written it's not that difficult to
> keep it moving forward.  Even if you don't change anything, but just
> make sure the interface to the prior-written thing continues to work,
> it may be of use to some people.
> 

In new years 2019, will CAlive be in the form of source code, everything 
in a single directory, or an install program?

[toc] | [prev] | [next] | [standalone]

#139380

On 30/12/2018 04:42, Rick C. Hodgin wrote:
> I've had the idea for an "if cargo" block.  It is a standard if {}
> block, but one containing additional cargo prefixed by in, out, and
> enter keywords, to be contained within each if clause to run before,
> after, and when entering the if statement.
> 
> The enter clause is given specifically to relate to something that
> should be done, possibly to undo something done in the in clause,
> including possibly calling the out clause to undo that setup, and
> prepare it for whatever other code is needed within the block.

Why are proposing (at lest in c.l.c++) an unpleasant replacement for 
something the language already supports?

-- 
Ian.

[toc] | [prev] | [next] | [standalone]

#139381

On 1/2/2019 3:50 PM, Ian Collins wrote:
> On 30/12/2018 04:42, Rick C. Hodgin wrote:
>> I've had the idea for an "if cargo" block.  It is a standard if {}
>> block, but one containing additional cargo prefixed by in, out, and
>> enter keywords, to be contained within each if clause to run before,
>> after, and when entering the if statement.
>>
>> The enter clause is given specifically to relate to something that
>> should be done, possibly to undo something done in the in clause,
>> including possibly calling the out clause to undo that setup, and
>> prepare it for whatever other code is needed within the block.
> 
> Why are proposing (at lest in c.l.c++) an unpleasant replacement for 
> something the language already supports?

I am unaware of its existence.  Enlighten me, sir Ian.

-- 
Rick C. Hodgin

[toc] | [prev] | [next] | [standalone]

#139382

On 1/2/2019 3:54 PM, Rick C. Hodgin wrote:
> On 1/2/2019 3:50 PM, Ian Collins wrote:
>> Why are proposing (at lest in c.l.c++) an unpleasant replacement for 
>> something the language already supports?
> 
> I am unaware of its existence.  Enlighten me, sir Ian.

[crickets]

Cluck cluck cluck cluck.. :-)

-- 
Rick C. Hodgin

[toc] | [prev] | [next] | [standalone]

#139386

On Wednesday, 2 January 2019 21:28:19 UTC, Rick C. Hodgin  wrote:
> On 1/2/2019 3:54 PM, Rick C. Hodgin wrote:
> > On 1/2/2019 3:50 PM, Ian Collins wrote:
> >> Why are proposing (at lest in c.l.c++) an unpleasant replacement for 
> >> something the language already supports?
> > 
> > I am unaware of its existence.  Enlighten me, sir Ian.
> 
> [crickets]

Newsgroups are an asynchronous means of communication.
Your arbitrary time limits on replies are of no significance.

> Cluck cluck cluck cluck.. :-)

For someone so quick to take offense, you sure can be offensive.

[toc] | [prev] | [next] | [standalone]

#139388

On 1/3/2019 3:44 AM, mark.bluemel@gmail.com wrote:
> For someone so quick to take offense, you sure can be offensive.

1)  Where am I quick to take offense?

2)  Where was I being offensive?

-- 
Rick C. Hodgin

[toc] | [prev] | [next] | [standalone]

#139390

On Thursday, 3 January 2019 13:15:52 UTC, Rick C. Hodgin  wrote:
> On 1/3/2019 3:44 AM, mark.bluemel@gmail.com wrote:
> > For someone so quick to take offense, you sure can be offensive.
> 
> 1)  Where am I quick to take offense?

I have neither the time nor the inclination to enumerate, but your
response to my other recent post will suffice as an example. No, I
don't hate you, you're not worth the bother of hating.
 
> 2)  Where was I being offensive?

You have, of course, snipped your clucking, which was presumably intended
to suggest "chicken".

Note: I do not intend to continue this subthread - feel free to post a
rejoinder and consider yourself to have "had the last word".

[toc] | [prev] | [next] | [standalone]

#139395

 > On Thursday, 3 January 2019 13:15:52 UTC, Rick C. Hodgin  wrote:
 >> On 1/3/2019 3:44 AM, mark.bluemel@gmail.com wrote:
 >>> For someone so quick to take offense, you sure can be offensive.
 >>
 >> 1)  Where am I quick to take offense?
 >
 > I have neither the time nor the inclination to enumerate, but your
 > response to my other recent post will suffice as an example. No, I
 > don't hate you, you're not worth the bother of hating.

My reply to Ian was intended as humor.  I used a :-) on it to indi-
cate the same.  I happened to be in a particularly good mood yester-
day afternoon.

 >> 2)  Where was I being offensive?
 >
 > You have, of course, snipped your clucking, which was presumably intended
 > to suggest "chicken".

Yes.  I put a happy face on it.  I was attempting to be silly.

 > Note: I do not intend to continue this subthread - feel free to post a
 > rejoinder and consider yourself to have "had the last word".

Why would you continue?  Your point has no validity and all further
discussion would do is serve to indicate how you were mistaken.  Why
would you want to confront that?

-- 
Rick C. Hodgin

[toc] | [prev] | [next] | [standalone]

#139391 — You are so full of shit (Was: if cargo blocks)

In article <q0l1tv$uhe$1@dont-email.me>,
Rick C. Hodgin <rick.c.hodgin@gmail.com> wrote:
>On 1/3/2019 3:44 AM, mark.bluemel@gmail.com wrote:
>> For someone so quick to take offense, you sure can be offensive.
>
>1)  Where am I quick to take offense?

All the time.

>2)  Where was I being offensive?

All the time.

-- 

First of all, I do not appreciate your playing stupid here at all.

	- Thomas 'PointedEars' Lahn -

[toc] | [prev] | [next] | [standalone]

#139397

W dniu czwartek, 3 stycznia 2019 14:15:52 UTC+1 użytkownik Rick C. Hodgin napisał:
> On 1/3/2019 3:44 AM, mark.bluemel@gmail.com wrote:
> > For someone so quick to take offense, you sure can be offensive.
> 
> 1)  Where am I quick to take offense?
> 
> 2)  Where was I being offensive?
> 
you are a dork, dik
every dork is sorta offensive
(youre also a spamer and spamers are also
offensie, youre imbecile and imbeciles are also offensive - except in places wher they are welcome, normal programming group is not for imbeciles)

[toc] | [prev] | [next] | [standalone]

#139401

On 03/01/2019 10:29, Rick C. Hodgin wrote:
> On 1/2/2019 3:54 PM, Rick C. Hodgin wrote:
>> On 1/2/2019 3:50 PM, Ian Collins wrote:
>>> Why are proposing (at lest in c.l.c++) an unpleasant replacement for
>>> something the language already supports?
>>
>> I am unaware of its existence.  Enlighten me, sir Ian.
> 
> [crickets]

Cricket, singular.  One of the joys of summer.

-- 
Ian

[toc] | [prev] | [next] | [standalone]

#139403

On 1/3/2019 2:11 PM, Ian Collins wrote:
> On 03/01/2019 10:29, Rick C. Hodgin wrote:
>> On 1/2/2019 3:54 PM, Rick C. Hodgin wrote:
>>> On 1/2/2019 3:50 PM, Ian Collins wrote:
>>>> Why are proposing (at lest in c.l.c++) an unpleasant replacement for
>>>> something the language already supports?
>>>
>>> I am unaware of its existence.  Enlighten me, sir Ian.
>>
>> [crickets]
> 
> Cricket, singular.  One of the joys of summer.
> 

Man, one time in particular, I saw a cluster of crickets being invaded 
by a bunch of ravenous ants in South Lake Tahoe. Each ant was around a 
half inch in length. The crickets were fish bait anyway, so their 
enclosure had holes in it for ventilation. The damn ants raided it. By 
the time I noticed the attack, they were tearing cricket limbs off to 
immobilize them, many dead: Terrible. There was another victim, a large 
june bug was being carefully dissected by the riled up ants. Should ants 
be sent to hell: Burned forever with a magnifying glass, perhaps even a 
solar furnace? ;^)

https://youtu.be/KAiVUn_ukdI
(yellow crazy ants murdering crabs!)

wow.

[toc] | [prev] | [next] | [standalone]

#139404

On 1/3/2019 5:11 PM, Ian Collins wrote:
> On 03/01/2019 10:29, Rick C. Hodgin wrote:
>> On 1/2/2019 3:54 PM, Rick C. Hodgin wrote:
>>> On 1/2/2019 3:50 PM, Ian Collins wrote:
>>>> Why are proposing (at lest in c.l.c++) an unpleasant replacement for
>>>> something the language already supports?
>>>
>>> I am unaware of its existence.  Enlighten me, sir Ian.
>>
>> [crickets]
> 
> Cricket, singular.  One of the joys of summer.

Never played it.  Just below 0C here.  I, of course, was referring to
the noise made when no other sounds are being heard.  Just the crickets
making noise in the background.

     Awkward silence cricket sound:
     https://www.youtube.com/watch?v=DNGzaeLJrNU

-- 
Rick C. Hodgin

[toc] | [prev] | [next] | [standalone]

#139405

W dniu czwartek, 3 stycznia 2019 23:12:07 UTC+1 użytkownik Ian Collins napisał:
> On 03/01/2019 10:29, Rick C. Hodgin wrote:
> > On 1/2/2019 3:54 PM, Rick C. Hodgin wrote:
> >> On 1/2/2019 3:50 PM, Ian Collins wrote:
> >>> Why are proposing (at lest in c.l.c++) an unpleasant replacement for
> >>> something the language already supports?
> >>
> >> I am unaware of its existence.  Enlighten me, sir Ian.
> > 
> > [crickets]
> 
> Cricket, singular.  One of the joys of summer.
> 
dont know exactly what you call a cricket but in poland i live there are those end summer sounds in hot nights esp if i got window in the second room opened at night

thise emiters of that sounds are i think veru big green 'grashoppers' who sometimes are able to jump into the 
room, big like finger i could say

what is curious i dont heard them this summer...dont know why..the summer before i remember few nights they were quite loud

there is stil some dose of somewhat wild animals in my city, most surprising are the mooses, i once saw one dead at side of the road and was very surprised they live here... though besides obviously very lot of ild animals are simpl slaughtered even there is a big lack of various birds etc, this is tragedy all that species killed

[toc] | [prev] | [next] | [standalone]

#139387

On Wednesday, 2 January 2019 20:52:58 UTC, Rick C. Hodgin  wrote:
> On 1/2/2019 3:50 PM, Ian Collins wrote:
> > On 30/12/2018 04:42, Rick C. Hodgin wrote:
> >> I've had the idea for an "if cargo" block.  It is a standard if {}
> >> block, but one containing additional cargo prefixed by in, out, and
> >> enter keywords, to be contained within each if clause to run before,
> >> after, and when entering the if statement.
> >>
> >> The enter clause is given specifically to relate to something that
> >> should be done, possibly to undo something done in the in clause,
> >> including possibly calling the out clause to undo that setup, and
> >> prepare it for whatever other code is needed within the block.
> > 
> > Why are proposing (at lest in c.l.c++) an unpleasant replacement for 
> > something the language already supports?
> 
> I am unaware of its existence.  Enlighten me, sir Ian.

Given your unwillingness/inability to read programming language
documentation, your boundless ignorance is hardly surprising.

Your arrogance and hubris in believing you can improve on what you don't
understand is only slightly more surprising, sadly.

[toc] | [prev] | [next] | [standalone]

#139389

On 1/3/2019 3:44 AM, mark.bluemel@gmail.com wrote:
> On Wednesday, 2 January 2019 20:52:58 UTC, Rick C. Hodgin  wrote:
>> On 1/2/2019 3:50 PM, Ian Collins wrote:
>>> Why are proposing (at lest in c.l.c++) an unpleasant replacement for
>>> something the language already supports?
>>
>> I am unaware of its existence.  Enlighten me, sir Ian.
> 
> Given your unwillingness/inability to read programming language
> documentation, your boundless ignorance is hardly surprising.

I am aware of a great many things in C/C++.  And I do read documentation,
just not the standards.  And, I've tried to read them.  I can't do it.
It reads like legalese or something.  My mind is not equipped to process
what it says in a way that makes sense.  It would take someone sitting
down and explaining to me what I'm reading so I can re-format it into
the way I think.  I do not expect anyone to do that, so I am where I am
doing what I'm doing with that handicap.

> Your arrogance and hubris in believing you can improve on what you don't
> understand is only slightly more surprising, sadly.

Why don't you enlighten me, Mark?  Is your hatred of me so supreme
that you would keep me pinned down in my own ignorance rather than
reaching a hand out to try and lift me to some higher place?  What
would you call your refusal to help me when I'm explicitly asking
for help?

-- 
Rick C. Hodgin

[toc] | [prev] | [next] | [standalone]

#139392

On Thursday, 3 January 2019 13:18:16 UTC, Rick C. Hodgin  wrote:

> Why don't you enlighten me, Mark?

I have neither the time nor the inclination to try to tutor you. Others
better qualified than I have tried and I've seen the results.

[toc] | [prev] | [next] | [standalone]

#139393

On Thursday, January 3, 2019 at 8:43:46 AM UTC-5, mark.b...@gmail.com wrote:
> On Thursday, 3 January 2019 13:18:16 UTC, Rick C. Hodgin  wrote:
> 
> > Why don't you enlighten me, Mark?
> 
> I have neither the time nor the inclination to try to tutor you. Others
> better qualified than I have tried and I've seen the results.

This is a new thing, Mark.  if-cargo blocks do not exist in C or
C++.  Of course the same effect can be arrived at by employing
multiple different coding methodologies ... but the encapsulation
aspect is new.

-- 
Rick C. Hodgin

[toc] | [prev] | [next] | [standalone]

#139398

On 1/3/2019 5:19 AM, Rick C. Hodgin wrote:
> On 1/3/2019 3:44 AM, mark.bluemel@gmail.com wrote:
>> On Wednesday, 2 January 2019 20:52:58 UTC, Rick C. Hodgin  wrote:
>>> On 1/2/2019 3:50 PM, Ian Collins wrote:
>>>> Why are proposing (at lest in c.l.c++) an unpleasant replacement for
>>>> something the language already supports?
>>>
>>> I am unaware of its existence.  Enlighten me, sir Ian.
>>
>> Given your unwillingness/inability to read programming language
>> documentation, your boundless ignorance is hardly surprising.
> 
> I am aware of a great many things in C/C++.  And I do read documentation,
> just not the standards.  And, I've tried to read them.  I can't do it.

Be calm, and read with patience. I think you can do it Rick.


> It reads like legalese or something. 

Kind of, but it does get its points across.


> My mind is not equipped to process
> what it says in a way that makes sense. 

Keep on trying. Don't give up.



> It would take someone sitting
> down and explaining to me what I'm reading so I can re-format it into
> the way I think.  I do not expect anyone to do that, so I am where I am
> doing what I'm doing with that handicap.

Hire a tutor?



>> Your arrogance and hubris in believing you can improve on what you don't
>> understand is only slightly more surprising, sadly.
> 
> Why don't you enlighten me, Mark?  Is your hatred of me so supreme
> that you would keep me pinned down in my own ignorance rather than
> reaching a hand out to try and lift me to some higher place?  What
> would you call your refusal to help me when I'm explicitly asking
> for help?
> 

Humm...

[toc] | [prev] | [next] | [standalone]

#139400

On 03/01/2019 09:54, Rick C. Hodgin wrote:
> On 1/2/2019 3:50 PM, Ian Collins wrote:
>> On 30/12/2018 04:42, Rick C. Hodgin wrote:
>>> I've had the idea for an "if cargo" block.  It is a standard if {}
>>> block, but one containing additional cargo prefixed by in, out, and
>>> enter keywords, to be contained within each if clause to run before,
>>> after, and when entering the if statement.
>>>
>>> The enter clause is given specifically to relate to something that
>>> should be done, possibly to undo something done in the in clause,
>>> including possibly calling the out clause to undo that setup, and
>>> prepare it for whatever other code is needed within the block.
>>
>> Why are proposing (at lest in c.l.c++) an unpleasant replacement for
>> something the language already supports?
> 
> I am unaware of its existence.  Enlighten me, sir Ian.

Fibble as already answered this in his own inimitable style.

Something like this will do what you want in C++:

void f(bool some_test1)
{
   struct T1
   {
     bool cleaned {};
     T1() {}   // setup_for_test1
     ~T1() { if (!cleaned) cleanup(); }  // cleanup_for_test1
     void related_code_if_block_entered() {}
     void cleanup() { cleaned = true; }
   };

   T1 t1;

   if (some_test1)
   {
     t1.related_code_if_block_entered();
     // Code1 here for this test passing
   }
   else
   {
     t1.cleanup();
   }
}

-- 
Ian.

[toc] | [prev] | [standalone]

Page 4 of 4 — ← Prev page 1 2 3 [4]

Back to top | Article view | comp.lang.c

csiph-web