Re: lush2 beta release

Ralf Juengling <[email protected]> Wed, 16 Sep 2009 09:07:04 -0700 (PDT)
Newsgroups gmane.lisp.lush.devel
Message-ID <[email protected]>
  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---58492207-1512558360-1253117225=:26414
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by expn.cat.pdx.edu id
	n8GG75Cj005459


Hm, then it's probably easier to go with the second option,
where you would substitute -gblearn- by -float-:

? (defnamespace gblearn- '((-gbtype- -float-)))
=3D gblearn-

? (in-namespace* gblearn-
   (de f (y) (declare (-gbtype-) y) (1+ y))
   )
=3D (f)

? ^Pf
(lambda (y)
   (declare (-float-) y)
   (1+ y) )
=3D t


It looks like -gbtype- is only used in two files, so only the
definitions in those two would need to be wrapped in
'(in-namespace* gblearn- ..)'.

Ralf



On Wed, 16 Sep 2009, Yury Sulsky wrote:

> Ralf,
>
> I'm having a bit of trouble with this. I'm trying to get a simple
> example to work, something like this:
>
> (in-namespace* lush1- (defvar -gbtype- -flt-))
> (de f (y) (declare (-gbtype-) y) (1+ y))
>
> It looks like one of the changes between Lush 1 and Lush 2 is the use
> of symbol properties for type names. So while lush1 uses (eval
> :-gbtype-), lush2 uses (getp '-gbtype- 'type-syntax).
>
> Adding this:
>
> (putp '-gbtype- 'type-syntax (getp '-flt- 'type-syntax))
> (putp '-gbtype- 'srg-type    (getp '-flt- 'srg-type))
>
> fixes it in the interpreter, but I still get a compile error (with
> both dhc-make and dhc-make-sf):
>
> *** compiler : Unrecognized type specifier : (-gbtype-)
> *** in:   (declare (-gbtype-) y)
> *** from: (lambda (y) (declare (-gbtype-) y) (1+ y))
>
> Yury
>
> On Tue, Sep 15, 2009 at 11:10 PM, Ralf Juengling <[email protected]> =
wrote:
>>
>> I just looked at gblearn2 myself. It's probably easiest to start
>> out by replacing all dhc-make by dhc-make-sf, which means you
>> compile in the lush1- namespace.
>>
>> Another issue I saw is the use of idx-m2resize (defined in
>> libidx/idx-macros). I believe this used to be a type-generic
>> macro for resizing a matrix. There are similar but
>> type-specific macros defined in the same file. idx-m2resize
>> now is also type-specific and is for resizing mptr-matrices
>> (it was the logical name for it). Now you need to look what
>> type-specific macro is required in place of idx-m2resize
>> (e.g., idx-f2resize for float matrices).
>>
>>
>>
>> On Tue, 15 Sep 2009, Ralf Juengling wrote:
>>
>>> Hi Yuri,
>>>
>>> The names -float- etc. were bound to some black-magic
>>> macros. These macros are still there but are defined
>>> in the namespace lush1- for backwards compatibility.
>>>
>>> You have two options, you could either do
>>>
>>> (in-namespace* lush1-
>>>
>>> (defvar -gbtype- -float-)
>>> ...
>>>
>>> ) ; in-namespace*
>>>
>>> to bind the alternative names -gbtype- etc. to the old macros.
>>>
>>> Or you could do it the way it is done in the opengl-interface,
>>> that is, define a new namespace for the gblearn code to do
>>> the translations "-gptype- -> -float-" etc. In the end you
>>> do the compilation in the namespace lush1-. Take a look at the
>>> file packages/opengl/opengl.lsh.
>>>
>>> Ralf
>>>
>>>
>>>
>>> On Tue, 15 Sep 2009, Yury Sulsky wrote:
>>>
>>>> Hi Ralf,
>>>>
>>>> I'm taking a look at the gblearn2 package, but I'm not sure how to
>>>> translate
>>>> one piece of code to Lush2.
>>>>
>>>> The code defines a type:
>>>> (defvar -gbtype- -float-)
>>>>
>>>> This doesn't work anymore. Are types kept in a different namespace?
>>>>
>>>> Thanks,
>>>> Yury
>>>>
>>>> On Sep 15, 2009, at 11:30 AM, Ralf Juengling <[email protected]> w=
rote:
>>>>
>>>>> Folks,
>>>>>
>>>>> I was thinking about releasing a lush2 beta before
>>>>> releasing a final and now I think it's =A0 =A0a good idea.
>>>>> I will =A0 =A0announce the beta on freshmeat and hope to get
>>>>> a few more people interested in lush that way. If lush
>>>>> is to have a future, we need to work on building a
>>>>> community.
>>>>>
>>>>> I plan to do the release in a month from now, October
>>>>> 15. There are still a couple of =A0 =A0things on our todo list,
>>>>> https://sourceforge.net/apps/trac/lush/wiki/LushTwoTodoList,
>>>>> mostly package updates. But the documentation and our
>>>>> homepage also need to be looked =A0 =A0at. I do not plan to do
>>>>> all of these myself and ask that some folks on this list
>>>>> pick up =A0 =A0one or the other work item. Packages that are not
>>>>> fixed by October 15 will not be included in the beta
>>>>> distribution.
>>>>>
>>>>> Ralf
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------=
-----------
>>>>> Come build with us! The BlackBerry&reg; Developer Conference in SF,=
 CA
>>>>> is the only developer event you need to attend this year. Jumpstart=
 your
>>>>> developing skills, take BlackBerry mobile applications to market an=
d
>>>>> stay
>>>>> ahead of the curve. Join us from November 9&#45;12, 2009. Register
>>>>> now&#33;
>>>>> http://p.sf.net/sfu/devconf
>>>>> _______________________________________________
>>>>> Lush-devel mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/lush-devel
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------=
---------
>>> Come build with us! The BlackBerry&reg; Developer Conference in SF, C=
A
>>> is the only developer event you need to attend this year. Jumpstart y=
our
>>> developing skills, take BlackBerry mobile applications to market and =
stay
>>> ahead of the curve. Join us from November 9&#45;12, 2009. Register
>>> now&#33;
>>> http://p.sf.net/sfu/devconf
>>> _______________________________________________
>>> Lush-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/lush-devel
>>>
>>
>
---58492207-1512558360-1253117225=:26414
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
---58492207-1512558360-1253117225=:26414
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Lush-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lush-devel

---58492207-1512558360-1253117225=:26414--