Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ogl\-sample\]\s+Parameter\s+semantics\s+in\s+\.spec\s+files\s*$/: 8 ]

Total 8 documents matching your query.

1. [ogl-sample] Parameter semantics in .spec files (score: 1)
Author: Sven Panne <Sven_Panne@xxxxxxxxxxxxxxx>
Date: Tue, 19 Mar 2002 10:04:29 +0100
I'm a bit puzzled by the semantics of the .spec files: Given the 9 possible combinations of directions (in, out, in/out) and transfer types (value, reference, array), what do they mean exactly? E.g.
/archives/ogl-sample/2002-03/msg00004.html (8,549 bytes)

2. Re: [ogl-sample] Parameter semantics in .spec files (score: 1)
Author: Jon Leech <ljp@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 21 Mar 2002 01:31:00 -0800
In C-speak, roughly func(BarPointer foo) func(const Bar *foo) func(const Bar foo[<whatever>]) The generator scripts and spec files evolved over many years (judging from the comments, early work was a
/archives/ogl-sample/2002-03/msg00007.html (12,210 bytes)

3. Re: [ogl-sample] Parameter semantics in .spec files (score: 1)
Author: Sven Panne <Sven_Panne@xxxxxxxxxxxxxxx>
Date: Fri, 22 Mar 2002 09:57:45 +0100
OK, perhaps the example was not really good, but I still can't grasp the intended differences between e.g. param foo BarPointer in value and param foo Bar out reference They *are* quite arbitrary in
/archives/ogl-sample/2002-03/msg00010.html (13,471 bytes)

4. Re: [ogl-sample] Parameter semantics in .spec files (score: 1)
Author: Jon Leech <ljp@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 22 Mar 2002 01:41:11 -0800
There really isn't one from the standpoint of what the .spec files are used for today, though I wouldn't recommend using the prior form because it throws away some information and requires another ty
/archives/ogl-sample/2002-03/msg00011.html (11,574 bytes)

5. [ogl-sample] Parameter semantics in .spec files (score: 1)
Author: Sven Panne <Sven_Panne@xxxxxxxxxxxxxxx>
Date: Tue, 19 Mar 2002 10:04:29 +0100
I'm a bit puzzled by the semantics of the .spec files: Given the 9 possible combinations of directions (in, out, in/out) and transfer types (value, reference, array), what do they mean exactly? E.g.
/archives/ogl-sample/2002-03/msg00017.html (8,579 bytes)

6. Re: [ogl-sample] Parameter semantics in .spec files (score: 1)
Author: Jon Leech <ljp@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 21 Mar 2002 01:31:00 -0800
In C-speak, roughly func(BarPointer foo) func(const Bar *foo) func(const Bar foo[<whatever>]) The generator scripts and spec files evolved over many years (judging from the comments, early work was a
/archives/ogl-sample/2002-03/msg00020.html (12,306 bytes)

7. Re: [ogl-sample] Parameter semantics in .spec files (score: 1)
Author: Sven Panne <Sven_Panne@xxxxxxxxxxxxxxx>
Date: Fri, 22 Mar 2002 09:57:45 +0100
OK, perhaps the example was not really good, but I still can't grasp the intended differences between e.g. param foo BarPointer in value and param foo Bar out reference They *are* quite arbitrary in
/archives/ogl-sample/2002-03/msg00023.html (13,555 bytes)

8. Re: [ogl-sample] Parameter semantics in .spec files (score: 1)
Author: Jon Leech <ljp@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 22 Mar 2002 01:41:11 -0800
There really isn't one from the standpoint of what the .spec files are used for today, though I wouldn't recommend using the prior form because it throws away some information and requires another ty
/archives/ogl-sample/2002-03/msg00024.html (11,724 bytes)


This search system is powered by Namazu