Alexander Burger wrote:
> Hi Cle,
Hi Alex,
back from shopping outside, I read your explanations. Let me thank you.
Although I have read the reference manual several times (and have it
open while I am coding) I did oversee 'push' and 'queue' totally :-( But
I know about 'inc' but for my learning
Hi Cle,
> > (dm foos> () (mapcar cdr (val (: Foos))) )
>..
> Howevery only if the receiver is the class. If I use an instance as
> receiver, it would not work! I would like to code the method the way,
> that the method will work regardless if the receiver is a class or one
> of its instances; lik
Let me correct a wrong statement:
On Thu, Dec 10, 2009 at 08:32:38AM +0100, Alexander Burger wrote:
> The reason is that all inheritance mechanisms (message passing,
> lookup with 'meta', 'var:', etc) start searching one level above the
> current object.
This is only true for 'meta' and derived f
Alexander Burger wrote:
> Let me correct a wrong statement:
>
> On Thu, Dec 10, 2009 at 08:32:38AM +0100, Alexander Burger wrote:
>
>> The reason is that all inheritance mechanisms (message passing,
>> lookup with 'meta', 'var:', etc) start searching one level above the
>> current object.
>>
Alexander Burger wrote:
> Hi Cle,
Hi Alex,
>>> (dm foos> () (mapcar cdr (val (: Foos))) )
>> ..
>> Howevery only if the receiver is the class. If I use an instance
>> as receiver, it would not work! I would like to code the method the
>> way, that the method will work regardless if the receiver
Hi Cle,
> Perhaps we should propose a naming convention, that class variables
> should begin with an uppercase letter, whereas instance variables should
> begin with a lowercase letter.
This is a good idea.
We just need to be tolerant with that, as existing code won't obey that
rule yet. I proba
Hi Alex,
I would like to ask you, in which format the user documentation like
Reference Manual or Tutorial were written? In the distribution it is
contained as .html but is this also the format it is written in the
first place?
If I would like to patch (read: propose changes) to the documentation
Hi Cle,
> I would like to ask you, in which format the user documentation like
> Reference Manual or Tutorial were written? In the distribution it is
> contained as .html but is this also the format it is written in the
> first place?
Yes, directly typed as HTML into 'vim'.
> If I would like to
On Thu, Dec 10, 2009 at 01:18:03PM +0100, Alexander Burger wrote:
> applications. The only class variable I can find in the picoLisp release
> is 'dbf'. I'll change that to 'Dbf', as I believe that it is normally
> not used in applications.
Phew, I hope I didn't break anything ;-)
There was one m
Alexander Burger wrote:
(...)
> There was one more class variable, 'aux'. I changed that, too. The
> problem was that both 'dbf' and 'aux' exist also as object attributes,
> so I had to be very careful when changing some of them to upper case.
>
> I checked it in as new testing release. Any fee
hi all,
I can also confirm it builds and passes test OK on Snow Leopard Mac OSX.
I am just starting to learn picolisp, comming from a Python
backgrnd... should I wait for the 64 bit version? And if so how much
longer?
thnx
On Wed, Dec 9, 2009 at 11:55 PM, Jon Kleiser wrote:
> Hi Alex,
>
> You
Hi Boh Yap,
> I can also confirm it builds and passes test OK on Snow Leopard Mac OSX.
Great! Thanks.
> backgrnd... should I wait for the 64 bit version? And if so how much
> longer?
While the 64-bit version itself is finished, and quite good tested on
Linx meanwhile, building it on Snow Leopa
Hello,
today I tried to verify if using a database instead of Pilog facts would
speed up my processing. While trying this, I stumbled over the
following. Suppose:
(pool test)
(class +Test +Entity)
(rel id (+Ref +String))
(rel src (+Ref +String))
(rel tgt (+Ref +String))
(new '(+Test
hi Alex,
re: Mac OS X assembler, a quick check shows the followg:
(I have also include the output of 'man as' as an attachment)
BTW I'm running OS X 10.6.2, Developer Tools (XCode) 3.2
The working build of picolisp 32bit was from the testing version, the
stable version still gave problem as off D
I don't know exactly the circumstances of what you're trying to
achieve, but if I were you and needed to access by unique id I would
first use +Key in the relations:
(rel id (+Key +String))
Then I would use (db) to access (like you do but without the Pilog):
(db 'id '+Test "1")
I think that's t
Hi Cle,
let me first correct some errors:
> (pool test)
This is a funny one. As the value of 'test' is a function definition,
you get a rather strange database file ;-)
The name "test", on the other hand, will give a conflict as there
is a directory with that name. I take "x.db" for now:
Hi Boh Yap,
thanks for the info!
> .and $ ls /usr/libexec/gcc/darwin/ shows:
> i386/ ppc/ppc64/ x86_64/
So this looks quite promising :-)
> 2. In Apple's Developer Docs they admit its not updated...
> ...
> ..and in the addressing mode chapter, it doesn't mention 64 bit
> registers fo
17 matches
Mail list logo
