bugs: a hardware solution is probably the best long-term approach for the
[libale.git] / bugs / issue-4154d622c049ae964255e14d5d4d1a59f9dc505a.yaml
blobb1b5876c3c48ede29beaf2c90e3994906db7ef67
1 --- !ditz.rubyforge.org,2008-03-06/issue 
2 title: Consider allowing for frame constructor creation of CL buffer when passed buffer value is ((cl_mem) 0).
3 desc: ""
4 type: :task
5 component: libale
6 release: 
7 reporter: David Hilvert <dhilvert@auricle.dyndns.org>
8 status: :closed
9 disposition: :fixed
10 creation_time: 2009-02-11 16:35:44.970099 Z
11 references: []
13 id: 4154d622c049ae964255e14d5d4d1a59f9dc505a
14 log_events: 
15 - - 2009-02-11 16:37:27.735084 Z
16   - David Hilvert <dhilvert@auricle.dyndns.org>
17   - created
18   - |-
19     In particular, frame applications such as Irani-Peleg simulations might involve
20     read-write data, for which initial values might be unimportant (so that the
21     library could initialize the data area, instead of the client).
22 - - 2009-02-16 18:12:58.796500 Z
23   - David Hilvert <dhilvert@auricle.dyndns.org>
24   - closed with disposition fixed
25   - Constructor has been modified to remove the parameter under consideration.