Saturday, May 8, 2004, 11:39:03 PM, Dan Sugalski wrote:
> Another todo list task for the interested. A perl & linker thing.
>
> Right now, through the wonders of the Unix default linking
> conventions, every function in parrot gets exported whether we want
> them to be o
At 9:04 PM +0200 5/8/04, Ron Blaschke wrote:
On Wed, 5 May 2004 13:59:14 -0400, Dan Sugalski wrote:
Another todo list task for the interested. A perl & linker thing.
Right now, through the wonders of the Unix default linking
conventions, every function in parrot gets exported whether we want
On Wed, 5 May 2004 13:59:14 -0400, Dan Sugalski wrote:
>>> Another todo list task for the interested. A perl & linker thing.
>>>
>>> Right now, through the wonders of the Unix default linking
>>> conventions, every function in parrot gets exported whether we want
>>> them to be or not, and gen
On May 5, 2004, at 12:06 PM, Dan Sugalski wrote:
At 7:57 PM +0100 5/5/04, Nicholas Clark wrote:
On Wed, May 05, 2004 at 08:59:03AM -0400, Dan Sugalski wrote:
Yeah, that's what I'm figuring. The symbols themselves should be
cross-platform, modulo the odd prefix character, or so I hope. The
linker
On Wed, 5 May 2004 13:59:14 -0400, Dan Sugalski wrote:
>>Windows requires this export list, which is currently stored in the
>>"module-definition file" libparrot.def. However, Windows provides a
>>"nicer" way of doing this, by prefixing a declaration with
>>__declspec(dllexport) someFunction
>>Wi
At 7:57 PM +0100 5/5/04, Nicholas Clark wrote:
On Wed, May 05, 2004 at 08:59:03AM -0400, Dan Sugalski wrote:
Yeah, that's what I'm figuring. The symbols themselves should be
cross-platform, modulo the odd prefix character, or so I hope. The
linker magic is definitely going to be platform and lin
On Wed, May 05, 2004 at 08:59:03AM -0400, Dan Sugalski wrote:
> Yeah, that's what I'm figuring. The symbols themselves should be
> cross-platform, modulo the odd prefix character, or so I hope. The
> linker magic is definitely going to be platform and linker
> specific--we may have to throw in
At 7:16 PM +0200 5/5/04, Ron Blaschke wrote:
On Tue, 4 May 2004 08:34:55 -0400, Dan Sugalski wrote:
Another todo list task for the interested. A perl & linker thing.
Right now, through the wonders of the Unix default linking
conventions, every function in parrot gets exported whether we want
th
On Tue, 4 May 2004 08:34:55 -0400, Dan Sugalski wrote:
> Another todo list task for the interested. A perl & linker thing.
>
> Right now, through the wonders of the Unix default linking
> conventions, every function in parrot gets exported whether we want
> them to be or not, and generally we d
At 12:40 AM -0700 5/5/04, Jeff Clites wrote:
On May 4, 2004, at 5:34 AM, Dan Sugalski wrote:
The right way to fix this is to have a file with the acceptable
exportable symbols and a fix to the link stage to convince the
linker that it should *only* export these symbols.
I have this working locall
On May 4, 2004, at 5:34 AM, Dan Sugalski wrote:
The right way to fix this is to have a file with the acceptable
exportable symbols and a fix to the link stage to convince the linker
that it should *only* export these symbols.
I have this working locally on Mac OS X--I expect it will be rather
pl
11 matches
Mail list logo
