Re: [cf-dev] Moving Blockwise support out of the stack

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [cf-dev] Moving Blockwise support out of the stack

From: Kai <sophokles.kh@xxxxxxxxx>
Date: Thu, 25 Aug 2016 15:23:50 +0000
Delivered-to: cf-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/cf-dev>
List-help: <mailto:cf-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cf-dev>, <mailto:cf-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/cf-dev>, <mailto:cf-dev-request@eclipse.org?subject=unsubscribe>

If we are able to move it out of the stack to the application level as a set of utility classes then it would be "configurable" by definition. Client code can either use it or not :-)

On Thu, Aug 25, 2016 at 4:04 PM James Nguyen <james.huy.nguyen@xxxxxxxxx> wrote:

Hi,

Since this topic is in discussion, I'd suggest to have the Blockwise configurable. This would help to open doors for other algorithms.

James

References:
- [cf-dev] Moving Blockwise support out of the stack
  - From: Hudalla Kai (INST/ESY1)
- Re: [cf-dev] Moving Blockwise support out of the stack
  - From: Simon Bernard
- Re: [cf-dev] Moving Blockwise support out of the stack
  - From: James Nguyen

Prev by Date: Re: [cf-dev] Moving Blockwise support out of the stack
Next by Date: Re: [cf-dev] Moving Blockwise support out of the stack
Previous by thread: Re: [cf-dev] Moving Blockwise support out of the stack
Next by thread: Re: [cf-dev] Moving Blockwise support out of the stack
Index(es):
- Date
- Thread

Breadcrumbs